Method and apparatus for token-based access of related resources

ABSTRACT

According to one embodiment, an apparatus may store a plurality of tokens indicating that a user is attempting to access a resource. The apparatus may determine an authorization level for the user based at least in part upon the plurality of tokens. The authorization level may indicate whether the user is authorized to access the resource. The apparatus may then determine a related resource that shares a relationship with the resource, and determine that the authorization level indicates that the user is authorized to access the related resource. The apparatus may then communicate a decision token indicating that the user is authorized to access the resource and the related resource.

TECHNICAL FIELD

This disclosure relates generally to tokenization and, morespecifically, to access of related resources.

BACKGROUND

A security system may control a user's access to a resource. To gainaccess to the resource, the user may provide the security system withcredentials, such as a user ID and a password. The security system mayexamine these credentials and various other factors such as, forexample, factors associated with the user, the user's device, and thenetwork environment in deciding whether to grant or deny access to theuser. The security system may also perform several other functionsrelated to the user's access to the resource.

SUMMARY OF THE DISCLOSURE

According to one embodiment, an apparatus may store a plurality oftokens indicating that a user is attempting to access a resource. Theapparatus may determine an authorization level for the user based atleast in part upon the plurality of tokens. The authorization level mayindicate whether the user is authorized to access the resource. Theapparatus may then determine a related resource that shares arelationship with the resource, and determine that the authorizationlevel indicates that the user is authorized to access the relatedresource. The apparatus may then communicate a decision token indicatingthat the user is authorized to access the resource and the relatedresource.

Certain embodiments may provide one or more technical advantages. Atechnical advantage of one embodiment includes a more seamless userexperience as the user accesses resources. Certain embodiments of theinvention may include none, some, or all of the above technicaladvantages. One or more other technical advantages may be readilyapparent to one skilled in the art from the figures, descriptions, andclaims included herein.

BRIEF DESCRIPTION OF THE FIGURES

For a more complete understanding of the present invention and itsfeatures and advantages, reference is now made to the followingdescription, taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 illustrates a system for controlling access to a resource;

FIG. 2 illustrates the system of FIG. 1 chaining a container;

FIG. 3 is a flowchart illustrating a method of chaining a containerusing the system of FIG. 1;

FIG. 4 illustrates the system of FIG. 1 aggregating attributes;

FIG. 5 is a flowchart illustrating a method of aggregating attributesusing the system of FIG. 1;

FIG. 6 illustrates the system of FIG. 1 performing attributeabstraction;

FIG. 7 is a flowchart illustrating a method of performing attributeabstraction using the system of FIG. 1;

FIG. 8 illustrates the system of FIG. 1 making an access decision;

FIG. 9 illustrates the levels determined by the system of FIG. 1 inmaking an access decision;

FIG. 10 is a flowchart illustrating a method of making an accessdecision;

FIG. 11 illustrates the system of FIG. 1 re-authenticating a user;

FIG. 12 is a flowchart illustrating a method of re-authenticating a userusing the system of FIG. 1;

FIG. 13 illustrates the system of FIG. 1 combining authenticationmethods;

FIG. 14 is a flowchart illustrating a method of combining authenticationmethods using the system of FIG. 1;

FIG. 15 illustrates the system of FIG. 1 reassigning privileges;

FIG. 16 is a flowchart illustrating a method of reassigning privilegesusing the system of FIG. 1;

FIG. 17 illustrates the system of FIG. 1 prioritizing packets;

FIG. 18 is a flowchart illustrating a method of prioritizing packetsusing the system of FIG. 1;

FIG. 19 illustrates the system of FIG. 1 conditioning an accessdecision;

FIG. 20 is a flowchart illustrating a method of conditioning accessdecisions using the system of FIG. 1;

FIG. 21 illustrates the system of FIG. 1 making an access decision for arelated resource;

FIG. 22 is a flowchart illustrating a method of making an accessdecision for a related resource using the system of FIG. 1;

FIG. 23 illustrates the system of FIG. 1 updating risk in real-time;

FIG. 24 is a flowchart illustrating a method of updating risk inreal-time using the system of FIG. 1;

FIG. 25 illustrates the system of FIG. 1 combining risk ratings;

FIG. 26 is a flowchart illustrating a method of combining risk ratingsusing the system of FIG. 1;

FIG. 27 illustrates the system of FIG. 1 tagging transactions;

FIG. 28 is a flowchart illustrating a method of tagging transactionsusing the system of FIG. 1;

FIG. 29 illustrates the system of FIG. 1 performing context caching;

FIG. 30 is a flowchart illustrating a method of performing contextcaching using the system of FIG. 1;

FIG. 31 illustrates the system of FIG. 1 performing virtual machinerecycling;

FIG. 32 is a flowchart illustrating a method of performing virtualmachine recycling;

FIG. 33 illustrates the system of FIG. 1 performing token termination;

FIG. 34 is a flowchart illustrating a method of performing tokentermination using the system of FIG. 1;

FIG. 35 illustrates the system of FIG. 1 detecting tampering;

FIG. 36 is a flowchart illustrating a method of detecting tamperingusing the system of FIG. 1;

FIG. 37 is a high level architectural diagram of a system that does notuse tokens to control access to a resource; and

FIG. 38 is a high level architectural diagram of a system that usestokens to control access to a resource.

DETAILED DESCRIPTION OF THE FIGURES

Embodiments of the present invention and its advantages are bestunderstood by referring to FIGS. 1 through 36, like numerals being usedfor like and corresponding parts of the various drawings.

FIG. 1 illustrates a system 100 for controlling access to a resource145. As provided in FIG. 1, system 100 may include a device 114, anetwork 120, a TBAC module 110, a resource provider 140, a network tokenprovider 122, a computed risk token provider 124, a public tokenprovider 126, and a private token provider 128. Device 114, resourceprovider 140, and TBAC module 110 may be coupled to network 120. Ingeneral, TBAC module 110 may use tokens 115 to control access by a user112 to a resource 145 provided by resource provider 140. When user 112uses device 114 to request a resource 145 from resource provider 140,TBAC module 110 may intercept the request and determine if user 112should be granted access to the resource 145. TBAC module 110 may makethis determination by examining tokens 115 from various token providers.Tokens 115 may provide TBAC module 110 with information associated withuser 112, device 114, and network 120. After examining tokens 115, TBACmodule 110 may grant access, deny access or condition access to theresource 145. Although this disclosure describes system 100 includingspecific elements, this disclosure contemplates system 100 including anysuitable elements to perform the described operations of system 100. Forexample, system 100 may include more token providers than the oneslisted above. System 100 may also operate across several networks 120.

In particular embodiments, system 100 may be operable to maketoken-based access decisions in lieu of attribute-based accessdecisions. For example, system 100 may examine and process tokens 115 indetermining whether to grant a user 112 access to a resource 145. System100 may also communicate and receive communications in the form oftokens 115. In particular embodiments, tokens 115 may represent aplurality of properties, qualities, or features, also known asattributes, belonging to a user 112, a device 114, a network 120, or aresource 145. A token 115 may represent hundreds or even thousands ofattributes. Although this disclosure describes tokens 115 representingattributes of particular elements, this disclosure contemplates tokens115 representing attributes of any element of system 100. In particularembodiments, tokens 115 may also represent a plurality of other tokens115. In this manner, system 100 may use tokens 115 to communicationinformation about attributes and other tokens 115.

Tokens 115 may be generated by TBAC module 110 and the various tokenproviders, such as for example, the public token provider 126. Eachtoken 115 may have a type that depends upon the source of the token 115.As an example and not by way of limitation, token 115 may be a publictoken 115 a, private token 115 b, resource token 115 c, risk token 115m, data token 115 e, or network token 115 f pursuant to the particulartoken provider that generated the token 115. Although this disclosuredescribes token 115 being of particular types, this disclosurecontemplates tokens 115 being of any suitable type to perform theoperations of system 100. Specific token types will be discussed furtherbelow. Because system 100 is a token-based system, system 100 mayprocess a plurality of attributes and tokens 115 in the form of a token115 rather than separately processing the individual attributes ortokens 115. In this manner, system 100 may make more efficient andquicker access decisions.

System 100 may include a user 112 and device 114. As an example and notby way of limitation, device 114 may be a personal computer, aworkstation, a laptop, a wireless or cellular telephone, an electronicnotebook, a personal digital assistant, or any other device (wireless,wireline, or otherwise) capable of receiving, processing, storing,and/or communicating information with other components of system 100.Device 114 may also include a user interface, such as a display, amicrophone, keypad, or other appropriate terminal equipment usable byuser 112. In particular embodiments, device 114 may be configured torequest and consume resources 145 provided by resource provider 140. Insome embodiments, an application executed by device 114 may request andconsume the resource 145. Although this disclosure describes device 114with respect to particular types of devices, this disclosurecontemplates device 114 being any suitable device.

In particular embodiments, device 114 may be operable to sendinformation to identify device 114 to other system 100 components. As anexample and not by way of limitation, device 114 may send a MAC address,IP address, and/or device name to identify device 114 to system 100components. Although this disclosure describes device 114 sendingparticular types of information used to identify device 114, thisdisclosure contemplates device 114 sending any suitable information usedto identify device 114. In particular embodiments, device 114 may beoperable to send information to verify device 114 is compliant toconsume a requested resource 145. As an example and not by way oflimitation, device 114 may send an OS version, firmware version, and/oroperating speed. Although this disclosure describes device 114 sendingparticular types of information used to verify the compliance of device114, this disclosure contemplates device 114 sending any suitableinformation used to verify the compliance of device 114.

User 112 may use device 114 to send information to identify orauthenticate user 112 to other system 100 components. As an example andnot by way of limitation, user 112 may send a user ID and/or a password.Although this disclosure describes user 112 using device 114 to sendparticular types of information used to identify user 112, thisdisclosure contemplates user 112 using device 114 to send any suitableinformation used to identify user 112.

System 100 includes network 120. Device 114 may communicate with TBACmodule 110 and resource provider 140 through network 120. Thisdisclosure contemplates any suitable network 120 operable to facilitatecommunication between the components of system 100, such as device 114and TBAC module 110. Network 120 may include any interconnecting systemcapable of transmitting audio, video, signals, data, messages, or anycombination of the preceding. Network 120 may include all or a portionof a public switched telephone network (PSTN), a public or private datanetwork, a local area network (LAN), a metropolitan area network (MAN),a wide area network (WAN), a local, regional, or global communication orcomputer network, such as the Internet, a wireline or wireless network,an enterprise intranet, or any other suitable communication link,including combinations thereof, operable to facilitate communicationbetween the components.

System 100 includes resource provider 140. Resource provider 140 may beoperable to provide resources 145 to be consumed by device 114. As anexample and not by way of limitation, resource provider 140 may providedevice 114 an instance of an application from a cloud. As anotherexample, resource provider 140 may provide computing power and send theresults of a computation to device 114. Resource 145 may also be, forexample, a service, an application, or a virtual machine. In particularembodiments, resource provider 140 may be operable to send resourcetokens 115 c to TBAC module 110. Resource tokens 115 c may identify thetypes of resources 145 provided by resource provider 140. Resourcetokens 115 c may also identify the types of resources 145 requested bydevice 114. As an example and not by way of limitation, a particularresource token 115 c may indicate that resource provider 140 has beenrequested to provide a financial application to device 114. Resourceprovider 140 may further include a policy enforcement point. Inparticular embodiments, the policy enforcement point may restrict orexclude user 112 from accessing a resource 145 until TBAC module 110grants access to user 112.

System 100 may include public token provider 126, network token provider122, computed risk token provider 124, private token provider 128, anddata token provider 129. These token providers may provide TBAC module110 with particular types of tokens 115. Public token provider 126 mayprovide public tokens 115 a (standardized and non-standardized), such asfor example, Kerberos and SAML tokens. Network token provider 122 mayprovide network tokens 115 f used to determine the status,vulnerability, congestion, etc. of network 120. Private token provider128 may provide private tokens 115 b, such as for example, custom tokensand private key tokens. Data token provider 129 may provide data tokens115 e, such as for example, tokens 115 representing social securitynumbers, dates, or email addresses. Computed risk token provider 124 maycalculate risk tokens 115 m indicating the risk associated with grantinguser 112 and/or device 114 access to a requested resource 145 overnetwork 120. When an element of device 114 or network 120 changes,computed risk token provider 124 may update the risk token 115 massociated with granting access to resource 145.

Each token 115 may represent a set of attributes that describe user 112,device 114, network 120, or an action or set of actions performed byuser 112. It may take hundreds or thousands of attributes to fullydescribe user 112, device 114, network 120, and a set of actionsperformed by user 112. Because of the large number of attributes used,it may be faster and more efficient to examine tokens 115, that embodyor represent a set or group of attributes, rather than the individualattributes when making a determination of whether to grant or denyaccess to a resource or service. In particular embodiments, system 100may provide more efficient access control because system 100 makesaccess decisions based on tokens 115 rather than attributes. Because anaccess decision may depend upon thousands of attributes, the accessdecision may be quickened if system 100 examined tokens 115 that wereabstracted from groups of attributes. By examining tokens 115 ratherthan attributes, TBAC module 110 may focus on processing access rulesrather than identifying attributes and attribute relationships.

When particular changes occur in user 112, device 114, network 120, orresource provider 140, the various token providers, device 114, orresource provider 140 may generate and send a new token 115 to TBACmodule 110. The new token 115 may represent the state of user 112,device 114, network 120, or resource provider 140 after the change. Thenew token 115 may trigger TBAC module 110 to perform a particularprocess or action in response to the new state. As an example and not byway of limitation, if user 112 attaches a peripheral device, such as aUSB drive, to device 114, then device 114 may generate and send a newtoken 115 to TBAC module 110 to indicate the presence of the peripheraldevice, and computed risk token provider 124 may calculate and send TBACmodule 110 a new risk token 115 g taking into account the presence ofthe peripheral device. In response, TBAC module 110 may produce an erroror terminate the session if the new risk token 115 g indicates theperipheral device presents an unacceptable risk.

In particular embodiments, system 100 may include TBAC module 110. TBACmodule 110 may include a processor 132 coupled to a memory 134. TBACmodule 110 may be coupled to and may receive tokens 115 from publictoken provider 126, network token provider 122, computed risk tokenprovider 124, and private token provider 128. TBAC module 110 mayexamine tokens 115 from the various token providers to determine if user112 and device 114 should be granted access to a resource 145 orservice.

TBAC module 110 may include memory 134. Memory 134 may store, eitherpermanently or temporarily, data, operational software, or otherinformation for processor 132. Memory 134 may include any one or acombination of volatile or non-volatile local or remote devices suitablefor storing information. For example, memory 134 may include randomaccess memory (RAM), read only memory (ROM), magnetic storage devices,optical storage devices, or any other suitable information storagedevice or a combination of these devices. Memory 134 may store tokens115 and any relationships amongst the tokens 115. In particularembodiments, memory 134 may further store sets of token-based rules 130.Rules 130 may direct how TBAC module 110 responds to a particular set ofreceived tokens 115.

Memory 134 may store four particular sets of token-based rules 130, eachcorresponding to a particular operation of TBAC module 110. The firstset of rules 130 is the container chaining rules discussed with respectto FIGS. 2 and 3. The second set of rules 130 is the attributeaggregation and assimilation rules discussed with respect to FIGS. 4 and5. The third set of rules 130 is the attribute abstraction rulesdiscussed with respect to FIGS. 6 and 7. The fourth set of rules 130 isthe tabular trust and transaction rules discussed with respect to FIGS.8-10. Each set of rules 130 may facilitate a function of the TBAC module110. For example, the tabular trust and transaction rules may facilitatethe grant or denial of access to a resource 145 by TBAC module 110.

TBAC module 110 may include processor 132. Processor 132 may control theoperation and administration of TBAC module 110 by processinginformation received from network 120 and memory 134. Processor 132 mayinclude any hardware and/or software that operates to control andprocess information. For example, processor 132 may examine a set oftokens 115 and apply a token-based rule 130 associated with the set oftokens 115. Processor 132 may be a programmable logic device, amicrocontroller, a microprocessor, any suitable processing device, orany suitable combination of the preceding.

In operation, TBAC module 110 may perform four primary functions:chaining containers, aggregating attributes, abstracting attributes, andmaking access decisions. In chaining containers, TBAC module 110 mayexamine a set of tokens 115 to determine if a device 114 is capable ofconsuming a requested resource 145. This function will be discussedfurther with respect to FIGS. 2 and 3. In aggregating attributes, TBACmodule 110 may retrieve, as tokens 115, the attributes required to grantaccess to a particular resource 145. This function will be discussedfurther with respect to FIGS. 4 and 5. In abstracting attributes, TBACmodule 110 may communicate a plurality of tokens 115 to be used in thecomputing of a risk token 115 m. This function will be discussed furtherwith respect to FIGS. 6 and 7. In making an access decision, TBAC module110 may examine a plurality of tokens 115 to determine whether to grantaccess, deny access, or condition access to a resource 145. Thisfunction will be discussed further with respect to FIGS. 8-10.

In addition, TBAC module 110 may perform four other categories offunctions as described in this disclosure. The first category offunctions pertains to user 112: re-authentication, combiningauthentication methods, reassigning privileges, and packetprioritization. During re-authentication, TBAC module 110 may promptuser 112 for a one-time password generated using the personalinformation of the user 112. This function will be discussed furtherwith respect to FIGS. 11 and 12. During combining authenticationmethods, TBAC module 110 may examine multiple authentication methods todetermine if a particular combination of authentication methods leads tothe assignment of a privilege to user 112. This function will bediscussed further with respect to FIGS. 13 and 14. During reassigningprivileges, TBAC module 110 may detect a change that poses a riskassociated with granting the user 112 a certain privilege, and mayupdate the privileges accordingly. This function will be furtherdiscussed with respect to FIGS. 15 and 16. During packet prioritization,TBAC module 110 may prioritize the packets of a high priority user 112over the packets of users 112 with a lower priority. This function willbe further discussed with respect to FIGS. 17 and 18.

The second category of functions pertains to access decisions:conditioning, accessing related resources, real-time risk updating,combining risk ratings, and transaction tagging. During conditioning,TBAC module 110 may determine any conditions associated with an accessdecision, and may communicate the conditions. This function will befurther discussed with respect to FIGS. 19 and 20. During accessingrelated resources, TBAC module 110 may determine if a user 112 mayaccess any resources 145 related to a requested resource 145. Thisfunction will be further discussed with respect to FIGS. 21 and 22.During real-time risk updating, TBAC module 110 may update the riskassociated with granting a user 112 or device 114 access to a resource145 in real-time, even as the device 114 may be consuming the resource145. This function will be discussed further with respect to FIGS. 23and 24. During combining risk ratings, TBAC module 110 may examinemultiple risk ratings associated with granting access to variousresources to determine a composite risk associated with user 112 anddevice 114. This function will be discussed further with respect toFIGS. 25 and 26. During transaction tagging, TBAC module 110 may detectsuspicious transactions and tag them for monitoring and isolation. Thisfunction will be discussed further with respect to FIGS. 27 and 28.

The third category of functions pertains to devices 114 and tokenproviders: context caching and virtual machine recycling. During contextcaching, an attribute cache may be cleansed and updated based on tokens115 involved in a risk computation. This function will be discussedfurther with respect to FIGS. 29 and 30. During VM recycling, TBACmodule 110 may facilitate the recycling of stale virtual machines. Thisfunction will be discussed further with respect to FIGS. 31 and 32.

The fourth category of functions pertains to tokens 115: tokentermination and tamper detection. During token termination, TBAC module110 may terminate and initialize tokens 115 for particular resourcesbased on risk. This function will be discussed further with respect toFIGS. 33 and 34. During tamper detection, TBAC module 110 may detect ifa token 115 has been tampered, and if so, may re-generate that token115. This function will be discussed further with respect to FIGS. 35and 36. Although particular functions have been previewed above inconjunction with particular figures in order to organize the subjectmatter for the reader, it should be understood that the presentdisclosure contemplates any suitable number and combination ofcomponents and functions regardless of any specific reference to thefigures.

The functions of the TBAC module 110 described herein may be performedby executing software stored in one or more non-transitory storagemedia, such as a computer-readable medium or any other suitable tangiblemedium. In particular embodiments, TBAC module 110 or any other suitablecomponent such as, for example, processor 132, may execute softwarestored in the one or more storage media to perform any of the functionsof the TBAC module 110 described herein.

In particular embodiments, because TBAC module 110 communicates andprocesses tokens 115 rather than attributes and because TBAC module 110operates on multiple types of tokens 115 from different sources, ratherthan only one type of token (for example, a subject token 115 b), TBACmodule 110 may make quicker and more efficient decisions with moregranularity and particularity as to user 112, device 114, network 120,and the requested resource 145. TBAC module 110 may consider a largenumber of attributes and tokens 115 by examining only a few tokens 115.This may reduce the processing time and memory profile associated withany particular operation. Further advantages may be readily apparentfrom the present disclosure.

FIGS. 2 and 3 illustrate how system 100 may perform the containerchaining function to prepare a device 114 to consume a resource 145.Prior to granting device 114 access to the resource 145, device 114 isprovisioned with an appropriate container 210 that is capable offacilitating access to and consumption of the resource 145. For example,the device 114 may be provisioned a container 210 that includes avirtual machine that can be used to consume the resource 145. Prior toprovisioning such a container 210, however, system 100 ensures that thedevice 114 is compliant, among other things. This process of checkingthe compliance of the device 114 and subsequently provisioning acontainer 210 to the device 114 is referred to as container chaining andwill be described in greater detail with respect to FIGS. 2 and 3.

When system 100 receives an initial request 240 from device 114 foraccess to a particular resource 145, system 100 may first identifydevice 114 and then verify that device 114 is compliant for consumingthe requested resource 145. By identifying device 114 and verifying itscompliance, system 100 may reduce the chances of granting device 114access to a resource 145 it cannot consume. For example, if device 114contains old versions of firmware or obsolete hardware, it may not bedesirable to grant device 114 access to a resource 145 that requiresupdated firmware or to a resource 145 that requires fast processingspeeds. After system 100 identifies device 114 and verifies that device114 is compliant, system 100 may provision a container 210 to device114. Container 210 may facilitate access to and consumption of theresource 145. In particular embodiments, system 100 may use tokens 115to perform the container chaining function thereby increasing the speedand efficiency at which system 100 may perform the function.

FIG. 2 illustrates the system 100 of FIG. 1 chaining a container 210. Asprovided in FIG. 2, TBAC module 110 may direct the container chainingprocess. The first task is for TBAC module 110 to identify device 114.After device 114 requests a resource 145, represented by resource token115 c, from resource provider 140, TBAC module 110 may intercept therequest 240 and request device 114 to identify itself. In response,device 114 may send identifying information 220 to a public tokenprovider 126 or to a private token provider 128. As an example and notby way of limitation, device 114 may send a MAC address, an IP address,and/or a device name. Public token provider 126 or private tokenprovider 128 may provide TBAC module 110 with a hard token 115 g thatrepresents the identifying information 220 sent by device 114. Althoughthis disclosure describes hard token 115 g representing particularinformation 220 used to identify device 114, this disclosurecontemplates hard token 115 g representing any suitable information 220that identifies device 114, such as for example, information from Layer2 of the Open Systems Interconnection (OSI) stack. Although thisdisclosure describes a singular hard token 115 g representingidentification information of device 114, this disclosure contemplatesany number and combination of hard tokens 115 g representing theidentification information 220. Resource provider 140 may further sendto TBAC module 110 resource token 115 c representing resource 145.Although this disclosure describes a singular resource token 115 crepresenting resource 145, this disclosure contemplates any number andcombination of resource tokens 115 c representing resource 145.

After TBAC module 110 identifies device 114, TBAC module 110 may verifythe compliance of device 114 to reduce the chances of granting device114 access to a resource 145 that device 114 cannot consume. TBAC module110 may use container chaining (CCC1) rules 230 stored in memory 134 tofacilitate verifying the compliance of device 114. TBAC module 110 mayuse hard token 115 g and resource token 115 c to access CCC1 rules 230.By using CCC1 rules 230, TBAC module 110 may verify the compliance ofdevice 114 to consume the requested resource 145 and may facilitate theprovisioning of container 210 to device 114. As an example and not byway of limitation, a particular CCC1 rule 230 may specify certaincompliance criteria in order for a device 114 identified by hard token115 g to consume the resource 145 associated with resource token 115 c.For example, CCC1 rule 230 may specify that device 114 containparticular versions of firmware or operating system, or that device 114meet particular hardware requirements. TBAC module 110 may determine theparticular CCC1 rule 230 using hard token 115 g and resource token 115c. TBAC module 110 may determine the compliance criteria from thedetermined CCC1 rule 230. In particular embodiments, TBAC module 110 mayrequest and in response, receive another hard token 115 g representingthe compliance information of device 114, and TBAC module 110 may verifydevice 114 is compliant by comparing the compliance information againstthe determined compliance criteria. As an example and not by way oflimitation, a particular CCC1 rule 230 may specify that a device 114should be operating a particular version of firmware in order to consumethe resource 145. TBAC module 110 may receive another hard token 115 grepresenting the firmware version of the device 114. TBAC module 110 maythen verify that device 114 contains a valid version of firmware bycomparing the firmware version of device 114 with the particularfirmware version specified by CCC1 rule 230. In particular embodiments,TBAC module 110 may quarantine device 114 until device 114 verifies thatit is compliant or capable of consuming the requested resource 145pursuant to CCC1 rule 230. After verifying that device 114 is compliant,TBAC module 110 may generate or receive a compliance token 115 h. TBACmodule 110 may then correlate hard token 115 g and compliance token 115h in order to associate device 114 with its compliance information.

After device 114 has been deemed compliant, TBAC module 110 maycommunicate the compliance token 115 h to facilitate the provisioning ofcontainer 210 to device 114. Container 210 may facilitate theconsumption of the resource 145. In particular embodiments, container210 may include a virtual machine operable to execute an applicationthat consumes the requested resource 145. The virtual machine may be anapplication that executes on device 114 to simulate the operation ofanother device or a cloud resource. After device 114 has beenprovisioned with container 210, TBAC module 110 may receive a virtualmachine (VM) token 115 i. TBAC module 110 may correlate VM token 215 cwith hard token 115 g and compliance token 115 h so that informationassociated with container 210 may be associated with device 114.

In particular embodiments, TBAC module 110 may generate and correlate asession token 115 j with hard token 115 g, compliance token 115 h, andVM token 115 i in order to associate device 114 and container 210 to asession. Resource token 115 c may also be associated with session token115 j. Session token 115 j may represent the session. In particularembodiments, the session may facilitate access by device 114 to theresource 145. After correlating hard token 115 g, compliance token 115h, VM token 115 i, and session token 115 j, any changes that occur todevice 114 or to container 210 may alter or terminate the session. As anexample and not by way of limitation, if a virus or malware is detectedon device 114, TBAC module 110 may detect a new or altered token 115associated with device 114 and terminate the session associated withsession token 115 j. Upon termination of the session, container 210 maybe released. As another example and not by way of limitation, if aperipheral device is attached to device 114, TBAC module 110 may detecta token 115 associated with the peripheral device, then TBAC module 110may pause the session. TBAC module 110 may recheck the compliance ofdevice 114 (i.e., to check if device 114 is allowed to consume therequested resource 145 when device 114 has a peripheral deviceattached). If device 114 is compliant, TBAC module 110 may continue thesession associated with session token 115 j. In particular embodiments,TBAC module 110 may communicate to device 114, by way of tokens 115,that a session has been terminated or paused.

In particular embodiments, TBAC module 110 may perform the containerchaining function to verify that a device 114 is compliant to reduce thechances of granting device 114 access to a resource 145 that it cannotconsume. Furthermore, verifying compliance may make it more probablethat device 114 may consume the resource 145 at an acceptable pace. Asan example and not by way of limitation, if device 114 included obsoletehardware, TBAC module 110 may deny access because granting access maylead to slow execution. In particular embodiments, because TBAC module110 uses tokens 115 rather than attributes in performing the containerchaining function, TBAC module 110 may quickly and efficiently verifythat device 114 is compliant.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 2, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 2 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 2 includes all the elements of system 100 inFIG. 1.

FIG. 3 is a flowchart illustrating a method 300 of chaining a container210 using the system 100 of FIG. 1. TBAC module 110 may perform method300. As provided in FIG. 3, TBAC module 110 may begin by intercepting arequest 240 from a device 114 to a resource 145 in step 310. Inresponse, TBAC module 110 may proceed to identify device 114. Toidentify device 114, TBAC module 110 may request identifying information220 from the device 114 in step 320. Identifying information 220 may bea MAC address, an IP address, a device name, or any suitable informationused to identify the device 114. In response to the request, TBAC module110 may receive a hard token 115 g in step 330. Hard token 115 g mayrepresent identifying information 220 of the device 114. In step 340,TBAC module 110 may determine if the hard token 115 g properlyidentifies the device 114. If the hard token 115 g does not properlyidentify the device 114, TBAC module 110 may return to step 320 torequest identifying information 220 from the device 114. If the hardtoken 115 g does properly identify the device 114, TBAC module 110 mayconsider device 114 identified and continue to verify the compliance ofdevice 114.

TBAC module 110 may verify that device 114 is compliant to consume theresource. By verifying that device 114 is compliant, TBAC module 110 mayreduce the chances of granting access to a resource 145 that device 114cannot consume. TBAC module 110 may begin verifying compliance in step350 by requesting compliance information from the device 114. Complianceinformation may indicate whether the device 114 is capable of consumingthe requested resource 145. In response to the request, TBAC module 110may receive a hard token 115 g representing the compliance informationof the device 114 in step 355. TBAC module 110 may then access CCC1rules 230 in step 360 to compare the compliance information of thedevice 114 against compliance criteria specified by a particular CCC1rule 230. In step 365, TBAC module 110 may determine, based on the CCC1rule 230, whether the device 114 is compliant to consume the resource145. If the device 114 is not compliant, TBAC module 110 may move tostep 370 by waiting for the device 114 to become compliant. As anexample and not by way of limitation, device 114 may be incompliantbecause the firmware in device 114 needs to be updated. TBAC module 110may wait for device 114 to update its firmware before proceeding to thenext step. If the device 114 becomes compliant, TBAC module 110 mayreturn to step 350 and request compliance information from the device114.

If the device 114 is compliant for the requested resource 145, TBACmodule 110 may generate a compliance token 115 h in step 375. Thecompliance token 115 h may represent the compliance of device 114. TBACmodule 110 may then conclude by communicating the compliance token 115 hto facilitate the provisioning of a container 210 to the device 114 instep 380. In particular embodiments, the container 210 may facilitateaccess by the device 114 to the resource 145.

In particular embodiments, correlating hard tokens 115 g, compliancetokens 115 h, VM tokens 115 i, resource tokens 115 c, and session token115 j, may provide more efficient handling of the identification andverification of device 114. Rather than examining thousands ofattributes used to identify device 114 and the requested resource 145,TBAC module 110 may examine session token 115 j and the tokens 115correlated with it to discover the state of device 114 and container210. By following method 300, TBAC module 110 may more efficientlyidentify and verify device 114 for consuming the requested resource 145.

FIGS. 4 and 5 illustrate how system 100 may perform the attributeaggregation function. In general, user 112 may be authenticated in orderto access resource 112. During the authentication process, variousproperties, qualities, or features of user 112 may be examined. Theseproperties, qualities, or features may be known as attributes 425.However, there may be thousands or millions of available attributes 425that describe user 112, and resource 145 may not require all availableattributes 425 be examined to grant access. If all available attributes425 were considered, the authentication process may be slow andinefficient. The process by which TBAC module 110 determines andretrieves only those attributes 425 required to grant access to theresource 145 is known as attribute aggregation and is discussed in moredetail with respect to FIGS. 4 and 5.

User 112 may begin the authentication process by providingauthentication information, such as, for example, a user ID and apassword, to gain access to a requested resource 145. TBAC module 110may receive a subject token 115 k from the various token providers thatrepresents the authentication information provided by user 112. However,resource provider 140 may require extra layers of authentication orextra authentication information associated with user 112 beforeresource provider 140 grants access to the requested resource 145. Theseextra layers of authentication or extra authentication information maybe in the form of attributes 425 associated with user 112 stored inrepositories 420 a-d. One solution would be for TBAC module 110 toretrieve all the attributes 425 associated with user 112 from therepositories 420 a-d. However, the resource provider 140 may not requireall the attributes 425 associated with user 112 to grant access to theresource 145. As an example and not by way of limitation, resourceprovider 140 may require the age of the user 112, but not the locationof the user 112 to grant access to resource 145. In particularembodiments, TBAC module 110 may determine, from an attributeaggregation (AAA1) rule 430, the set of attributes 440 required byresource provider 140 to grant access to resource 145. In particularembodiments, the set of attributes 440 may not be required to grantaccess to resource 145, but may be preferred or prioritized in makingthe determination to grant access to resource 145. TBAC module 110 maythen determine from subject token 115 k a set of attributes 445 alreadyprovided by user 112. TBAC module 110 may then determine, from the setof required attributes 440 and the set of provided attributes 445, a setof attributes 450 that are still missing and request only thoseattributes 425 from the repositories 420 a-d. In particular embodiments,TBAC module 110 may provide faster and more efficient authentication byretrieving only the attributes 425 necessary to access the resource 145.

FIG. 4 illustrates the system 100 of FIG. 1 aggregating attributes 425.As provided in FIG. 4, TBAC module 110 may have correlated hard token115 g, compliance token 115 h, and VM token 115 i, among others, asappropriate, to session token 115 j thus indicating that device 114 hasbeen identified and verified compliant and that a container 210 has beenprovisioned to device 114 according to the container chaining functiondescribed with respect to FIGS. 2 and 3. User 112 may now initiate theauthentication process by providing initial attributes, such as forexample, initial authentication information to access a resource 145.Resource 145 may be represented by resource token 115 c, which may alsobe sent to and stored in TBAC module 110. In particular embodiments,after the user 112 has provided initial authentication information, suchas for example, a user ID and password, in the form of subject token 115k, TBAC module 110 may determine a set of required attributes 440required to access the requested resource 145. System 100 may theninspect subject token 115 k to determine a set of provided attributes445. System 100 may then compare the set of provided attributes 445 andthe set of required attributes 440 to determine a set of missingattributes 450. System 100 may then request the missing attributes fromrepositories 420 a-d. System 100 may then receive at least one moresubject token 115 k representing the missing attributes from the varioustoken providers, and correlate the at least one more subject token 115 kto the session token 115 j. In this manner, system 100 may provide amore efficient user authentication scheme by retrieving only theattributes 425 necessary to access the requested resource 145.

TBAC module 110 may determine the set of required attributes 440 usingAAA1 rules 430 stored in memory 134. A particular AAA1 rule 430 mayindicate a set of required attributes 440 required by resource provider140 to grant user 112 access to a particular resource 145. In particularembodiments, TBAC module 110 may use a stored token 115, such as theresource token 115 c, and the subject token 115 k to determine theparticular AAA1 rule 430. By using AAA1 rules 430, TBAC module 110 maydetermine and retrieve only those attributes 440 required to accessresource 145. TBAC module 110 may examine the subject token 115 kassociated with user 112 to determine a set of provided attributes 445.TBAC module 110 may then determine a set of missing attributes 450 bycomparing the set of required attributes 440 and the set of providedattributes 445. As an example and not by way of limitation, a particularAAA1 rule 430 may specify that accessing a particular resource 145requires the time of login and the social security number of the user112 in addition to the user ID and password of the user 112. However,subject token 115 k may represent only the user ID and password of theuser 112. In this case, TBAC module 110 may determine that the time oflogin and the social security number are in the set of missingattributes 450.

After determining the set of missing attributes 450, TBAC module 110 mayrequest the missing attributes 450 from various correspondingrepositories 420 a-d. Each repository 420 a-d may correspond with one ofthe various token providers. Each repository 420 a-d may storeattributes 425 a-d associated with user 112. As an example and not byway of limitation, data repository 420 c may store data attributes 425 cassociated with user 112 such as a social security number or telephonenumber. Each repository 420 a-d may return, to a corresponding tokenprovider, the attributes 425 a-d requested by TBAC module 110. Eachtoken provider may then generate and send a token 115 that representsthe returned attributes 425 to TBAC module 110, such as for example, anew subject token 115 k 2. TBAC module 110 may then correlate the newsubject token 115 k 2 to session token 115 j. TBAC module 110 mayfurther store the new subject token 115 k 2 in memory 134. Using theprevious example, TBAC module 110 may determine the time of login andthe social security number of the user 112 are in the set of missingattributes 450. TBAC module 110 may then request the time of login andthe social security number from the corresponding repositories, such asfor example, the data repository 420 c. In response, the data repository420 c may return, to the data token provider 129, the social securitynumber of the user. The data token provider 129 may generate a newsubject token 115 k 2 representing the social security number of theuser 112, and send the new subject token 115 k 2 to TBAC module 110. Asimilar process may be followed by the private repository 420 b toreturn the time of login. In this manner, TBAC module 110 may provide amore efficient authentication scheme by retrieving only the attributes440 required by resource provider 140 to access the requested resource145.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 4, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 4 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 4 includes all the elements of system 100 inFIG. 1.

FIG. 5 is a flowchart illustrating a method 500 of aggregatingattributes 425 using the system 100 of FIG. 1. TBAC module 110 mayperform method 500. As provided in FIG. 5, TBAC module 110 may begin bystoring a hard token 115 g, compliance token 115 h, VM token 115 i, anda session token 115 j, among others, as appropriate, in step 510. Thesetokens 115 may be correlated and stored pursuant to the processdiscussed with respect to FIGS. 2 and 3. TBAC module 110 may continue byreceiving a subject token 115 k indicating a user attempt toauthenticate in step 520. The subject token 115 k may indicate a userattempt to authenticate by representing certain attributes 425 of theuser 112 such as, for example, a user ID and password. TBAC module 110may continue by determining the attributes 425 represented by thesubject tokens 115 k in step 530. These attributes 425 may be the set ofprovided attributes 445. TBAC module 110 may continue by accessing AAA1rules 430 in step 540. AAA1 rules 430 may specify all the attributes 425required to access resource 145. These specified attributes 425 may bethe set of required attributes 440. In step 550, TBAC module 110 maydetermine from the set of required attributes 440 and the set ofprovided attributes 430 if there are missing attributes 450 required toaccess the requested resource 145. If there are no missing attributes450, TBAC module 110 may conclude by correlating the subject token 115 kto the session token 115 j in step 595. However, in particularembodiments, the attributes 425 represented by the subject token 115 kmay not be sufficient to grant access to a requested resource 145. Inthat situation, method 500 may determine that there are missingattributes 450 in step 550. Accordingly, TBAC module 110 may determinethe missing attributes 450 in step 560.

To retrieve the missing attributes 450, TBAC module 110 may continue bysending a request for the missing attributes 450 to the correspondingrepositories 420 a-d in step 570. In response to the request, method 500may receive tokens 115 representing the missing attributes 450 in step580. In step 590, TBAC module 110 may determine if, according to theAAA1 rules 430, all missing attributes 450 have been represented by thereceived tokens 115. If not, TBAC module 110 may return to step 560 andrequest the still missing attributes 450. If all missing attributes 450have been represented by the received tokens 115, TBAC module 110 mayconclude by correlating the received tokens 115 with the session token115 j in step 595. By performing method 500, TBAC module 110 may providea more efficient authentication scheme by retrieving only the attributes425 required by resource provider 140 to access the requested resource145.

In particular embodiments, attribute aggregation allows system 100 toprovide a faster and more efficient authentication process bydetermining and retrieving only the attributes 440 required to accessresource 145. Furthermore, because TBAC module 110 processes all theattributes 425 using tokens 115, system 100 may perform theauthentication process even faster than if it considered individualattributes 425.

FIGS. 6 and 7 illustrate how system 100 may perform the attributeabstraction function. In general, TBAC module 110 may facilitate thegeneration of new tokens 115 from a particular set of tokens 620, notjust attributes 425. Prior to generating the new token 115, TBAC module110 may determine whether the particular set of tokens 620 is present.If the particular set of tokens 620 is present, TBAC module maycommunicate the particular set of tokens 620 to a token provider. Thetoken provider may generate the new token 115 that represents aparticular aspect of the particular set of tokens 620. This process isknown as attribute abstraction, which is discussed further with respectto FIGS. 6 and 7 in the context of generating a risk token 115 m.Although this disclosure describes the attribute abstraction functionusing a particular context, this disclosure contemplates performing theattribute abstraction function in any suitable context.

TBAC module 110 may perform attribute abstraction to facilitate thegeneration of a risk token 115 m. In particular embodiments, TBAC modulemay determine that a particular set of tokens 620 is ready forabstraction. Then, TBAC module 110 may generate a dataset token 115 lrepresenting the set of tokens 620, and communicate the dataset token115 l to the computed risk token provider 122. In response, the computedrisk token provider 122 may compute and return a risk token 115 massociated with the set of tokens 620.

FIG. 6 illustrates the system 100 of FIG. 1 performing attributeabstraction. As provided in FIG. 6, TBAC module 110 may store a hardtoken 115 g, compliance token 115 h, VM token 115 i, and subject token115 k, among others, as appropriate. These tokens 115 may be correlatedwith session token 115 j, also stored in TBAC module 110. TBAC module110 may also receive and store resource token 115 c from resourceprovider 140. In particular embodiments, resource tokens 115 c may becorrelated with session token 115 j. In particular embodiments, thesetokens 115 may form a set of tokens 620. To perform attributeabstraction, TBAC module 110 may determine whether the set of tokens 620is ready for abstraction. As an example and not by way of limitation,TBAC module 110 may determine that the set of tokens 620 containssufficient tokens 115 for a risk token 115 m to be computed. In responseto this determination, TBAC module 110 may communicate information aboutthe set of tokens 620 to facilitate generation of the risk token 115 m.

In particular embodiments, TBAC module 110 may store attributeabstraction (AAA2) rules 630 in memory 134. AAA2 rules 630 may specifywhen a particular set of tokens 620 is ready for abstraction. As anexample and not by way of limitation, a particular AAA2 rule 630 mayspecify that a set of tokens 620 is ready for abstraction when the setof tokens 620 includes a subject token 115 k, a hard token 115 g, acompliance token 115 h, a VM token 115 i, and a session token 115 j. Ifthe particular set of tokens 620 includes those tokens 115, then TBACmodule 110 may generate a dataset token 115 l that represents the set oftokens 620. In particular embodiments, dataset token 115 l may be usedto communicate information about the set of tokens 620. The informationabout the set of tokens 620 may be used to perform attributeabstraction.

To complete the attribute abstraction process, TBAC module 110 maycommunicate the dataset token 115 l to a token provider. In particularembodiments, TBAC module 110 may communicate the dataset token 115 l tocomputed risk token provider 122. In response, computed risk tokenprovider 122 may evaluate the set of tokens 620 represented by datasettoken 115 l and compute a risk associated with the set of tokens 620. Asan example and not by way of limitation, the risk may be associated withgranting user 112 (associated with subject token 115 k) and device 114(associated with hard token 115 g) access to the resource 145(associated with resource token 115 c). Computed risk token provider 122may generate a risk token 115 m to represent the computed risk. Computedrisk provider 122 may communicate the risk token 115 m to TBAC module110. When TBAC module 110 receives the risk token 115 m, it maycorrelate it with session token 115 j. In this manner, TBAC module 110may perform attribute abstraction by taking a set of tokens 620 andabstracting another token 115, such as a risk token 115 m, thatrepresents a particular aspect associated with the set of tokens 620. Inthis example, the aspect is the risk associated with granting a user 112access to a resource 145 associated with the set of tokens 620.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 6, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 6 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 6 includes all the elements of system 100 inFIG. 1.

FIG. 7 is a flowchart illustrating a method 700 of performing attributeabstraction using the system 100 of FIG. 1. TBAC module 110 may performmethod 700. TBAC module 110 may begin by storing a hard token 115 g,compliance token 115 h, VM token 115 i, subject token 115 k, and sessiontoken 115 j, among others, as appropriate, as a plurality of tokens 115in step 710. In particular embodiments, the plurality of tokens 115 mayinclude a set of tokens 620 that is ready for abstraction. AAA2 rules630 may be used to determine if the set of tokens 620 is present. Instep 720, TBAC module 110 may access the AAA2 rules 630. Based on theAAA2 rules 630, TBAC module 110 may determine in step 730 whether theplurality of tokens 115 include a set of tokens 620 that is ready forabstraction. If the plurality of tokens 115 does not include a set oftokens 620 that is ready for abstraction, TBAC module 110 may conclude.

However, if the plurality of tokens 115 does include a set of tokens 620that is ready for abstraction, TBAC module 110 may complete theattribute abstraction process. To begin, TBAC module 110 may generate adataset token 115 l representing the plurality of tokens 115 in step740. TBAC module 110 may communicate the dataset token 115 l to thecomputed risk token provider 122 in step 750. In response, the computedrisk token provider 122 may compute a risk token 115 m. In step 760,TBAC module 110 may receive the risk token 115 m. TBAC module 110 mayconclude in step 770 by correlating the dataset token 115 l and the risktoken 115 m to the session token 115 j.

In particular embodiments, by performing the attribute abstractionfunction, system 100 may represent information about tokens 115, notjust attributes 425, in the form of tokens 115. In this manner, system100 may make more robust access decisions. Furthermore, by representinginformation about multiple tokens 115 in a single token 115, such as arisk token 115 m, system 100 may perform faster and more efficientevaluation of tokens 115.

FIGS. 8-10 illustrate how system 100 may make an access decision usingtokens 115. In general, TBAC module 110 may determine whether to grantor deny a user 112 access to a resource 145. TBAC module 110 may alsodetermine conditions to granting or denying access. This process ofdetermining whether to grant or deny access and determining anyconditions is referred to as making an access decision, which will bediscussed further with respect to FIGS. 8-10.

TBAC module 110 may make an access decision by using levels 850determined by tokens 115. In particular embodiments, TBAC module 110 mayuse tokens 115 to generate various levels 850 that indicate the securityand risks posed by a user 112, a device 114, and/or a network 120. TBACmodule 110 may then use these various levels 850 to make a decision togrant, deny, or condition access to the resource 145. TBAC module 110may further generate a decision token 115 n representing the decision togrant, deny, or condition access. TBAC module 110 may communicate thedecision token 115 n to facilitate enforcement of the access decision.In particular embodiments, by examining tokens 115 rather thanattributes 425 in making an access decision, TBAC module 110 mayincrease the speed and efficiency of the decision-making process. Byexamining tokens 115, TBAC module 110 may also lighten the processingload on processor 132 and memory 134 by focusing more on making theaccess decision rather than on individual attributes 425 and therelationships between the attributes 425.

FIG. 8 illustrates the system 100 of FIG. 1 making an access decision.As provided in FIG. 8, TBAC module 110 may store hard token 115 g,compliance token 115 h, VM token 115 i, subject token 115 k, datasettoken 115 l, and risk token 115 m, among others, as appropriate, as aset of tokens 620. TBAC module 110 may also include resource token 115 crepresenting a resource 145 and network token 115 f representing network120 in the set of tokens 620. These tokens 115 may further be correlatedwith session token 115 j pursuant to the functions described withrespect to FIGS. 2-7. These tokens 115 may indicate that a user 112 isrequesting access to the resource 145 over network 120. In particularembodiments, each token 115 may be associated with a layer in the OpenSystems Interconnection (OSI) stack. As an example and not by way oflimitation, network token 115 f may be associated with Layer 3 of theOSI stack. As another example and not by way of limitation, hard token115 g may be associated with Layer 2 of the OSI stack. By using thesetokens 115 in the set of tokens 620, TBAC module 110 may make an accessdecision when a user 112 requests access to a resource 145.

To make the access decision, TBAC module 110 may use the set of tokens620 to access tabular trust and transaction (TTT1) rules 830 stored inmemory 134. In particular embodiments, TTT1 rules 830 may specifyvarious levels 850 associated with the set of tokens 620. As an exampleand not by way of limitation, TTT1 rules 830 may specify that risk token115 m may determine a risk level, and that the more risk represented byrisk token 115 m, the higher the risk level may be. These levels 850 andtheir association with particular tokens 115 will be described furtherwith respect to FIG. 9. A particular TTT1 rule 830 may also specify anaccess decision associated with the various levels 850. As an exampleand not by way of limitation, a particular TTT1 rule 830 may specifythat access may be denied if the risk level is above a certainthreshold. TBAC module 110 may use a stored token 115, such as forexample, the risk token 115 m and the resource token 115 c to determinea particular TTT1 rule 830. Based on the access decision specified in aparticular TTT1 rule 830, TBAC module 110 may make a decision to grant,deny, or condition access to the resource 145. In particularembodiments, TBAC module 110 may then generate a decision token 115 nrepresenting an access decision.

In particular embodiments, the decision token 115 n may be communicatedby system 100 to facilitate enforcement of the access decision. As anexample and not by way of limitation, TBAC module 110 may communicatethe decision token 115 n to the resource provider 140 to facilitateenforcement of the access decision. As another example and not by way oflimitation, TBAC module 110 may communicate the decision token 115 n tothe device 114 to facilitate enforcement of the access decision. Afterreceiving the decision token 115 n, resource provider 140 or device 114may enforce the access decision. If the decision token 115 n representsa decision to grant access to the resource 145, then resource provider140 may grant access to resource 145 after it receives decision token115 n. If decision token 115 n represents a decision to deny access,then resource provider 140 may deny access to resource 145. Byleveraging tokens 115, TBAC module 110 may make faster and more granularaccess decisions.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 8 this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 8 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 8 includes all the elements of system 100 inFIG. 1.

FIG. 9 illustrates the levels 850 determined by the system 100 of FIG. 1in making an access decision 900. As provided in FIG. 9, access decision900 may depend upon four types of levels: integrity levels 910, trustlevels 920, risk levels 930, and identity assurance levels 940. Eachtype of level may take on a numerical value within a predefined rangesuch as, for example, 0 to 9, with higher numbers indicating a higherlevel of integrity, trust, risk, or identity assurance. Each type oflevel 850 may depend upon particular tokens 115 stored in TBAC module110. As an example and not by way of limitation, based on TTT1 rule 830,subject token 115 k and risk token 115 m may indicate a certain identityassurance level 940. In particular embodiments, the numerical value ofany particular level 850 may depend upon the OSI layer associated withthe particular tokens 115 associated with that level 850. As an exampleand not by way of limitation, a subject token 115 k representing anauthentication method from Layer 2 of the OSI stack may influence theidentity assurance level 940 more than a subject token 115 krepresenting an authentication method from Layer 7. Following will be adescription of the various types of levels 850 and how they may bedetermined.

Integrity levels 910 may indicate the quality and/or security of network120. A high integrity level may indicate that network 120 is safe fromintrusion by hackers, viruses, or malware. A high integrity level mayalso indicate that communications over network 120 may not experiencejitter or packet loss. In particular embodiments, integrity levels 910may be determined from network tokens 115 f and risk tokens 115 m. As anexample and not by way of limitation, integrity levels 910 may dependupon a trusted network connect (TNC) token, a netpath token, and/or anetwork access control (NAC) session token. Although this disclosuredescribes integrity levels 910 depending on particular tokens 115, thisdisclosure contemplates integrity levels 910 depending upon any suitabletokens 115. As an example and not by way of limitation, TBAC module 110may store a TNC token and a netpath token. TTT1 rule 830 may specifythat the integrity level 910 is a 6 if a TNC token and a netpath tokenare present. Based on TTT1 rule 830, TBAC module 110 may determine thatthe integrity level 910 is a 6 because the TNC token and the netpathtoken are present. In particular embodiments, when TBAC module 110receives a network token 115 f indicating a change in the network 120,TBAC module 110 may change integrity level 910 accordingly. The changedintegrity level 910 may cause user 112 to be denied or granted access toa resource 145.

Trust levels 920 may indicate the level of authentication or securityrequired or presented by resource 145. A high trust level may indicatethat resource 145 is a risk-sensitive resource that requires more secureforms of authentication in order to be accessed by user 112. Inparticular embodiments, trust levels 920 may be determined from resourcetoken 115 c and subject token 115 k. As an example and not by way oflimitation, trust levels 920 may depend upon trust tokens, certificatesas tokens, keys and signatures, digital fingerprint tokens, and anycustom tokens. As an example and not by way of limitation, TBAC module110 may store a trust token and a certificate as a token. TTT1 rule 830may specify that the trust level 920 is a 7 if a trust token and acertificate as a token are present. Based on TTT1 rule 830, TBAC module110 may determine that the trust level 920 is a 7 because the trusttoken and the certificate as a token are present. Although thisdisclosure describes trust level 920 depending upon particular types oftokens, this disclosure contemplates trust level 920 depending upon anysuitable types of tokens.

Risk levels 930 may indicate the overall risk associated with grantinguser 112 and device 114 access to resource 145 over network 120. Ahigher risk level may indicate that the user 112, device 114, and/ornetwork 120 presents a higher security risk associated with accessingthe resource 145. In particular embodiments, a higher risk level 930 mayindicate that more secure forms of authentication may be required toaccess the resource 145. As an example and not by way of limitation,user 112 may gain access to resource 145 despite a high risk level 930by providing higher levels of user authentication, for example, throughbiometric scans. Risk levels 930 may be determined from risk tokens 115m computed from dataset token 115 l, as described with respect to FIG.6. In particular embodiments, risk level 930 may be adjusted. As anexample and not by way of limitation, user 112 may lower risk level 930by securing network 120. Although this disclosure describes risk level930 depending upon particular types of tokens, this disclosurecontemplates risk level 930 depending upon any suitable types of tokens.

Identity assurance level 940 may indicate the strength of authenticationpresented by user 112 and device 114. A higher identity assurance level940 may indicate that user 112 has provided more secure forms ofauthentication. As an example and not by way of limitation, user 112 mayraise identity assurance level 940 by performing biometricauthentication. In particular embodiments, identity assurance levels 940may depend upon subject tokens 115 k and hard tokens 115 g. As anexample and not by way of limitation, identity assurance levels 940 maydepend upon Trusted Platform Module (TPM) tokens, Kerberos tokens,Security Assertion Markup Language (SAML) tokens, Single Sign-On (SSO)tokens, win SSO tokens, ping tokens, netegrity tokens, openauthentication tokens, MAC tokens, IP address tokens, user ID tokens,and password tokens. As an example and not by way of limitation, TBACmodule 110 may store a user ID token and a password token. TTT1 rule 830may specify that the identity assurance level 940 is a 2 if a user IDtoken and a password token are present. Based on TTT1 rule 830, TBACmodule 110 may determine that the identity assurance level 940 is a 2because the user ID token and the password token are present. Althoughthis disclosure describes identity assurance levels 940 depending uponparticular types of tokens, this disclosure contemplates identityassurance levels 940 depending upon any suitable types of tokens.

In particular embodiments, TBAC module 110 may use the integrity level910, trust level 920, risk level 930, and identity assurance level 940to make, based on TTT1 rule 830, an access decision 900. As an exampleand not by way of limitation, TTT1 rule 830 may indicate that in orderto grant access to a resource 145, integrity level 910, trust level 920,and identity assurance level 940 must be at least a 7. If, based on thetokens 115 correlated with session token 115 j, the integrity level 910is an 8, the trust level 920 is a 9, and the identity assurance level940 is a 6, then TBAC module 110 will deny access to the resource 145.If, however, the integrity level 910 is an 8, the trust level 920 is a9, and the identity assurance level 940 is a 7, then TBAC module 110will grant access to the resource 145. In particular embodiments, TBACmodule 110 may condition access to the resource 145. In such cases, TBACmodule 110 may attach conditions to the decision grant or deny access tothe resource 145. A more detailed description of conditioning access isprovided with respect to FIGS. 19 and 20.

FIG. 10 is a flowchart illustrating a method 1000 of making an accessdecision 900. TBAC module 110 may perform method 1000. As provided inFIG. 10, TBAC module 110 may begin by storing a hard token 115 g,compliance token 115 h, VM token 115 i, subject token 115 k, datasettoken 115 l, risk token 115 m, and a session token 115 j, among others,as appropriate, in step 1010. TBAC module 110 may continue by accessingthe TTT1 rules 830 in step 1020 to determine various levels 850. In step1030, TBAC module 110 may determine, by the TTT1 rules 830, an integritylevel 910 associated with risk token 115 m and network token 115 f. TBACmodule 110 may continue by determining, by the TTT1 rules 830, a trustlevel 920 associated with resource token 115 c and subject token 115 kin step 1040. In step 1050, TBAC module 110 may determine, by the TTT1rules 830, a risk level 930 associated with the risk token 115 m in step1040. TBAC module 110 may continue by determining, by the TTT1 rules830, an identity assurance level 940 associated with subject token 115 kand hard token 115 a in step 1060. After the various levels 850 havebeen determined, TBAC module 110 may determine what type of accessshould be granted to a requested resource 145 based on the integritylevel 910, trust level 920, risk level 930, and identity assurance level940 in step 1070. If TBAC module 110 determines access should be denied,then TBAC module 110 may generate a decision token 115 n representingthe denial of access in step 1080. If access should be granted, thenTBAC module 110 may generate a decision token 115 n representing thegrant of access in step 1085. If access should be conditioned, then TBACmodule 110 may generate a decision token 115 n representing theconditioning of access in step 1090. TBAC module 110 may conclude bycommunicating the decision token 115 n to a resource provider 140 tofacilitate enforcement of the access decision 900 in step 1070.

In particular embodiments, by examining tokens 115 rather thanattributes 425 in making an access decision 900, TBAC module 110 mayincrease the speed and efficiency of the decision-making process.Furthermore, by examining tokens 115, TBAC module 110 may lighten theprocessing load on processor 132 and memory 134 by focusing more onmaking the access decision 900 rather than on individual attributes 425and the relationships between the attributes 425.

FIGS. 11 and 12 illustrate system 100 performing the re-authenticationfunction. In general, TBAC module 110 may re-authenticate a user 112when a change occurs that challenges or puts into question the integrityof the authentication of user 112. TBAC module 110 may determine thatthe change sufficiently challenges the integrity of the authenticationof user 112. In response, TBAC module 110 may block the user 112 fromaccessing a resource and may request user 112 enter a password to regainaccess to the resource.

With regards to the re-authentication process, TBAC module 110 mayrequest the password be a one-time password (that is, a subsequentlygenerated password may not be the same as a previously generatedpassword) generated using the personal information of the user 112. TBACmodule 110 may then request user 112 to enter the one-time password.Included in the request 1110 may be a message instructing the user 112how to form the one-time password. If the user 112 enters the one-timepassword correctly, then TBAC module 110 may consider the user 112re-authenticated. This process of determining when a change sufficientlychallenges the integrity of the authentication of the user 112 and thesubsequent generation and request of a one-time password is referred toas re-authentication, which is discussed further with respect to FIGS.11 and 12.

FIG. 11 illustrates the system 100 of FIG. 1 re-authenticating a user112. As provided in FIG. 11, TBAC module 110 may store a plurality oftoken 115 to indicate that user 112 may be using device 114 to consumeresource 145 over network 120. TBAC module 110 may receive a token 115that indicates a change has occurred in network 120, resource 145, ordevice 114. As an example and not by way of limitation, token 115 mayindicate that traffic over network 120 is experiencing jitter. Asanother example and not by way of limitation, token 115 may indicatethat the access requirements of resource 145 may have changed. Althoughthis disclosure describes token 115 indicating particular changes, thisdisclosure contemplates token 115 indicating any changes in network 120,resource 145, or device 114.

In response to detecting token 115, TBAC module 110 may access userre-authentication (UUU1) rules 1130 stored in memory 134. In particularembodiments, UUU1 rules 1130 may specify what changes indicated by token115 trigger re-authentication. If a particular UUU1 rule 1130 specifiesthat the change indicated by token 115 triggers re-authentication, thenTBAC module 110 may begin the re-authentication process. As an exampleand not by way of limitation, if token 115 indicates that network 120 isexperiencing jitter and a particular UUU1 rule 1130 specifies thatjitter should trigger the re-authentication process, then TBAC module110 may initiate the re-authentication process.

TBAC module 110 may initiate the re-authentication process by requestingthe generation of a password using the personal information of the user112. TBAC module 110 may send the request to a token provider such as,for example, the private token provider 128. In response, the tokenprovider may generate the password using personal information of theuser 112. As an example and not by way of limitation, in response to therequest, private token provider 128 may generate the password byappending the birth year of the user 112 to the last three digits of thesocial security number of the user 112. Although this disclosuredescribes the generation of the password using particular types ofpersonal information, this disclosure contemplates the generation of thepassword using the age of the user 112, the number of children user 112has, the age of the spouse of user 112, or any other suitable personalinformation. In particular embodiments, the password may be a one-timepassword, that is, a subsequently generated password may not be the sameas a previously generated password. As an example and not by way oflimitation, in response to a second request following the previouslydescribed request, private token provider 128 may generate anotherpassword that does not use the same information as the previouslygenerated password.

In particular embodiments, after the token provider generates thepassword, the token provider may generate a re-authentication token 115o that represents the generated password. The token provider may thencommunicate the re-authentication token 115 o to TBAC module 110. TBACmodule 110 may use re-authentication token 115 o to generate a requestfor a second password 1110. The request for the second password 1110 mayinclude instructions on how to form the second password. As an exampleand not by way of limitation, if re-authentication token 115 o includesa password that was generated by appending the birth year of the user112 to the last three digits of the social security number of the user,then the request for the second password may include the message:“Please form the second password by appending your birth year to thelast three digits of your social security number.” In particularembodiments, TBAC module 110 may communicate the request for the secondpassword 1110 to device 114. User 112 may view the request for thesecond password 1110 and enter the second password using device 114.Device 114 may send a response 1120 that includes the second password toTBAC module 110. TBAC module 110 may then compare the passwordrepresented by re-authentication token 115 o and the second passwordincluded within the response 1120. If the password and the secondpassword match, TBAC module 110 may consider user 112 re-authenticated.If they do not match, TBAC module 110 may terminate a sessionrepresented by session token 115 j or TBAC module 110 may resend therequest for the second password 1110 to device 114.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 11, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 11 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 11 includes all the elements of system 100in FIG. 1.

FIG. 12 is a flowchart illustrating a method 1200 of re-authenticating auser 112 using the system 100 of FIG. 1. TBAC module 110 may performmethod 1200. As provided in FIG. 12, TBAC module 110 may begin bystoring a hard token 115 g, compliance token 115 h, VM token 115 i,subject token 115 k, network token 115 f, and resource token 115 c,among others, as appropriate, in step 1210. The hard token 115 g may beassociated with a device 114. The resource token 115 c may be associatedwith a resource 145. The network token 115 f may be associated with anetwork 120. TBAC module 110 may continue by detecting a change in thenetwork 120, resource 145, or device 114 in step 1220. In particularembodiments, TBAC module 110 may detect a token 115 representing thechange. In response, TBAC module 110 may continue by accessing UUU1rules 1130 in step 1230. In step 1240, TBAC module 110 may determine,based on UUU1 rules 1130, whether the change triggers re-authentication.If not, TBAC module 110 may conclude. If the change does triggerre-authentication, TBAC module 110 may continue to step 1250 to requesta re-authentication token 115 o.

In step 1260, TBAC module 110 may receive the re-authentication token115 o. In particular embodiments, the re-authentication token 115 o mayinclude a password generated using personal information of user 112. Thepassword may be a one-time password. In step 1270, TBAC module 110 mayrequest a second password. In the request for the second password, TBACmodule 110 may include instructions on how to form the second password.In step 1280, TBAC module 110 may receive the second password. In step1290, TBAC module 110 may determine if the password and the secondpassword match. If not, TBAC module 110 may return to step 1270 andrequest the second password. In particular embodiments, TBAC module 110may also conclude if the password and second password do not match. Ifthe password and the second password do match, TBAC module 110 maycontinue to step 1295 to re-authenticate the user 112.

In particular embodiments, because TBAC module 110 uses tokens 115 todetect changes and to administer the re-authentication process, TBACmodule 110 may leverage information from numerous sources such as thenetwork 120, resource 145, and device 114 to accurately trigger there-authentication process. Furthermore, because TBAC module 110 utilizesone-time passwords generated from the personal information of the user112 during the re-authentication process, TBAC module 110 may provide amore secure re-authentication.

FIGS. 13 and 14 illustrate the system 100 combining authenticationmethods. In general, a user 112 may perform multiple methods ofauthentication during any session. For each method of authenticationperformed, system 100 may grant the user 112 a privilege such as forexample, an access right, edit right, or distribution right. System 100may further grant the user 112 privileges based on combinations ofauthentication methods performed. The process of determining theparticular combinations of authentication methods that yield thegranting of privileges is referred to as combining authenticationmethods, which is discussed further with respect to FIGS. 13 and 14.

In particular embodiments, TBAC module 110 may store multiple subjecttokens 115 k that indicate a user 112 has performed multiple forms ofauthentication. Each form of authentication may be associated with thegranting of a privilege 1310. TBAC module 110 may examine the multiplesubject tokens 115 k to determine if particular combinations of thesubject tokens 115 k may lead to the granting of privileges 1310. If acombination of the subject tokens 115 k does lead to the granting of aprivilege 1310, TBAC module 110 may generate a privilege token 115 p torepresent the privilege 1310. Privilege token 115 p may then becommunicated to facilitate the granting of the privilege 1310.

FIG. 13 illustrates the system 100 of FIG. 1 combining authenticationmethods. As provided in FIG. 13, TBAC module 110 may store a pluralityof subject tokens 115 k. As an example and not by way of limitation,TBAC module 110 may store a first subject token 115 k 1 and a secondsubject token 115 k 2. First subject token 115 k 1 may be correlatedwith second subject token 115 k 2. In particular embodiments, eachsubject token 115 k may indicate a different authentication method asanother subject token 115 k. As an example and not by way of limitation,first subject token 115 k 1 may indicate that user 112 has beenauthenticated with a user ID and password, and second subject token 115k 2 may indicate user 112 has been authenticated by providing correctanswers to security questions. Because each subject token 115 kindicates a particular authentication method, each subject token 115 kmay indicate a privilege 1310 or a set of privileges 1310 should begranted to user 112 for device 114. A privilege 1310 may grant a user112 the ability to perform certain operations. As an example and not byway of limitation, a privilege 1310 may grant the user 112 access to aresource, the ability to edit the resource, and/or the ability toterminate the resource. Although this disclosure describes privilege1310 granting the user 112 specific abilities, this disclosurecontemplates privilege 1310 granting the user 112 any suitable ability.

In particular embodiments, TBAC module 110 may detect whether acombination of authentication methods indicated by multiple subjecttokens 115 k may yield the granting of a privilege 1310. Using theprevious example, TBAC module 110 may detect a third subject token 115 k3 indicating user 112 has performed a third authentication method suchas a retina scan. TBAC module 110 may use the first subject token 115 k1, the second subject token 115 k 2, and the third subject token 115 k 3to access authentication method combination (III1) rules 1330 stored inmemory 134. III1 rules 1330 may specify the combinations ofauthentication methods that yield the granting of privileges 1310. TBACmodule 110 may use III1 rules 1330 to facilitate the granting ofprivileges 1310.

As an example and not by way of limitation, a particular III1 rule 1330may specify a privilege 1310 or a set of privileges 1310 to be grantedwhen a particular combination of authentication methods has beenperformed. Continuing the previous example, a particular III1 rule 1330may indicate that the combination of the user ID and passwordauthentication indicated by first subject token 115 k 1 and the retinascan authentication method indicated by third subject token 115 k 3yields the granting of a first privilege 1310 a. Another III1 rule 1330may specify that the combination of the security questionsauthentication method indicated by second subject token 115 k 2 and theretina scan authentication method indicated by third subject token 115 k3 yields the granting of a second privilege 1310 b. Yet another III1rule 1330 may specify that the combination of the user ID and passwordauthentication method indicated by first subject token 115 k 1, thesecurity questions authentication method indicated by second subjecttoken 115 k 2, and the retina scan authentication method indicated bythird subject token 115 k 3 yields the granting of a third privilege1310 c. Although this disclosure describes particular combinations ofsubject tokens 115 k yielding certain privileges 1310, this disclosurecontemplates any combination of any number of subject tokens 115 kyielding any number of privileges 1310. TBAC module 110 may use theseIII1 rules 1330 to facilitate the granting of first privilege 1310 a,second privilege 1310 b, and third privilege 1310 c to user 112.

To do so, TBAC module 110 may generate a privilege token 115 prepresenting the privileges 1310 granted to user 112. Continuing theprevious example, TBAC module 110 may generate a privilege token 115 prepresenting first privilege 1310 a, second privilege 1310 b, and thirdprivilege 1310 c granted as a result of particular combinations of firstsubject token 115 k 1, second subject token 115 k 2, and third subjecttoken 115 k 3. Privilege token 115 p may also represent other privileges1310 associated with the individual subject tokens 115 k.

In particular embodiments, TBAC module 110 may communicate privilegetoken 115 p to facilitate the granting of the privileges 1310represented by privilege token 115 p. As an example and not by way oflimitation, TBAC module 110 may communicate privilege token 115 p to aresource provider 140. In response, the resource provider 140 may grantuser 112 first privilege 1310 a, second privilege 1310 b, and thirdprivilege 1310 c associated with particular combinations of firstsubject token 115 k 1, second subject token 115 k 2, and third subjecttoken 115 k 3. In particular embodiments, TBAC module 110 may furthercorrelate the privilege token 115 p with the subject tokens 115 k.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 13, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 13 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 13 includes all the elements of system 100in FIG. 1.

FIG. 14 is a flowchart illustrating a method 1400 of combiningauthentication methods using the system 100 of FIG. 1. TBAC module 110may perform method 1400. As provided in FIG. 14, TBAC module 110 maybegin by storing a first subject token 115 k 1 indicating a firstauthentication method and a second subject token 115 k 2 indicating asecond authentication method in step 1410. As an example and not by wayof limitation, the first authentication method may be a user ID andpassword and the second authentication method may be providing correctanswers to a security question. TBAC module 110 may continue bydetecting a third subject token 115 k 3 indicating a thirdauthentication method in step 1420. Continuing the example, the thirdauthentication method may be a retina scan.

TBAC module 110 may determine whether particular combinations ofauthentication methods lead to the granting of privileges 1310. Tobegin, TBAC module 110 may access III1 rules 1330 in step 1430. In steps1440, 1450, and 1460, TBAC module 110 may determine based on III1 rules1330 whether particular combinations of the first subject token 115 k 1,the second subject token 115 k 2, and the third subject token 115 k 3yield the granting of particular privileges 1310. In step 1440, TBACmodule 110 may determine that the combination of the first and thirdauthentication methods yield the granting of a first privilege 1310 a.In step 1450, TBAC module 110 may determine that the combination of thesecond and third authentication methods yield the granting of a secondprivilege 1310 b. In step 1460, TBAC module 110 may determine thecombination of the first, second, and third authentication methodsyields the granting of a third privilege 1310 c.

If TBAC module 110 determines that the first privilege 1310 a, thesecond privilege 1310 b, and/or the third privilege 1310 c should begranted in steps 1440, 1450, and 1460, then TBAC module 110 may continueto steps 1470, 1480, and 1490 to indicate the first privilege 1310 a,the second privilege 1310 b, and/or the third privilege 1310 c should begranted. TBAC module 110 may continue to step 1495 to generate aprivilege token 115 p representing the privileges 1310 that should begranted. TBAC module 110 may conclude at step 1498 by communicating theprivilege token 115 p to facilitate the granting of the privileges 1310that should be granted.

In particular embodiments, because TBAC module 110 may examineparticular combinations of authentication methods to determine ifcertain privileges 1310 should be granted, system 100 may provide a morerobust process of determining and granting privileges 1310 to a user112. Furthermore, because TBAC module 110 examines tokens 115 ratherthan attributes 425 to determine the granting of privileges 1310, TBACmodule 110 may provide a faster and more efficient process ofdetermining and granting privileges.

FIGS. 15 and 16 illustrate system 100 reassigning privileges 1310. Ingeneral, a user 112 may be granted a privilege 1310 or set of privileges1310, and these privileges 1310 may define what actions the user 112 mayperform while accessing a resource 145. However, for security reasons,when changes occur in the system 100, the user 112 may be denied certainprivileges 1310 based on those changes. The process of detecting achange and determining which privileges 1310 to deny or grant isreferred to as reassigning privileges, which is discussed further withrespect to FIGS. 15 and 16.

TBAC module 110 may be facilitating access by a user 112 to resource 145over a network 120. User 112 may have been granted a privilege 1310associated with accessing resource 145. However, when TBAC module 110detects a change, for example in the network 120 or resource 145, it maynot be safe for the user 112 to continue having the privilege 1310. TBACmodule 110 may determine, based on the change, if the privilege 1310should be denied. If the privilege should be denied, TBAC module 110 maygenerate a token 115 that, when communicated, may facilitate the denialof privilege 1310.

FIG. 15 illustrates the system 100 of FIG. 1 reassigning privileges1310. As provided in FIG. 15, TBAC module 110 may store a subject token115 k, resource token 115 c, network token 115 f, risk token 115 m, andprivilege token 115 p, among others, as appropriate. These tokens 115may be correlated with a session token 115 j to indicate that user 112may be accessing a resource 145 through a session. Furthermore, resourcetoken 115 p may represent a set of privileges 1310 granted to user 112.Each privilege 1310 in the set of privileges 1310 d may grant user 112 acertain ability while device 114 consumes resource 145. As an exampleand not by way of limitation, a privilege 1310 in the set of privileges1310 d may grant user 112 the ability to edit resource 145.

TBAC module 110 may be monitoring the session while user 112 isaccessing resource 145. In particular embodiments, TBAC module 110 mayreceive a token 115 that indicates a change has occurred in system 100.This change may correspond to a change in any of the tokens 115 storedin TBAC module 110, and may affect the privileges 1310 granted to user112. TBAC module 110 may determine the effect of the change on the setof privileges 1310 d and facilitate the revoking and granting ofprivileges 1310 to user 112 pursuant to the privilege reassignmentprocess.

TBAC module 110 may initiate the privilege reassignment process bycommunicating token 115 and risk token 115 m to the computed risk tokenprovider 124. In response, computed risk token provider 124 mayrecompute risk token 115 m based on the change represented by token 115to produce a recomputed risk token 115 m 2. Computed risk token provider124 may communicate the recomputed risk token 115 m 2 to TBAC module110.

TBAC module 110 may use the recomputed risk token 115 m 2 to facilitatethe revoking and granting of privileges 1310. TBAC module 110 may userecomputed risk token 115 m 2 to access privilege reassignment (PPP2)rules 1530 stored in memory 134 to determine the privileges 1310 fromthe set of privileges 1310 d that should be revoked and granted based onthe risk associated with the change indicated by token 115. As anexample and not by way of limitation, a particular PPP2 rule 1530 mayspecify that, based on the change, a privilege 1310 to edit resource 145may be revoked and a privilege 1310 to email the resource 145 may begranted. TBAC module 110 may add to the set of privileges 1310 d theprivileges 1310 that should be granted, and remove from the set ofprivileges 1310 d the privileges 1310 that should be revoked. Continuingthe previous example, based on the particular PPP2 rule, TBAC module 110may remove from the set of privileges 1310 d the privilege 1310 to editresource 145 and add to the set of privileges 1310 d the privilege toemail the resource 145.

TBAC module 110 may add and remove privileges 1310 from the set ofprivileges 1310 d to form a new set of privileges 1310 e. TBAC module110 may generate a new privilege token 115 p 2 to represent the new setof privileges 1310 e. TBAC module 110 may then communicate the newprivilege token 115 p 2 to facilitate the reassignment of the newprivileges 1310 e to user 112. In particular embodiments, TBAC module110 may communicate the new privilege token 115 p 2 to resource provider140 to facilitate the granting and revoking of privileges 1310. Inresponse, resource provider 140 may revoke the privileges 1310 thatshould be revoked and grant the privileges 1310 that should be granted.In this manner, TBAC module 110 may use tokens 115 to reassignprivileges 1310 to user 112 during runtime. In particular embodiments,TBAC module 110 may further use recomputed risk token 115 m 2 to make anaccess decision 900 following the process discussed with respect toFIGS. 8-10.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 15, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 15 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 15 includes all the elements of system 100in FIG. 1.

FIG. 16 is a flowchart illustrating a method 1600 of reassigningprivileges 1310 using the system 100 of FIG. 1. TBAC module 110 mayperform method 1600. TBAC module 110 may begin by storing a subjecttoken 115 k, a resource token 115 c, a network token 115 f, a privilegetoken 115 p, a risk token 115 m, and a session token 115 j, amongothers, as appropriate, as a plurality of tokens 115 in step 1610. Instep 1620, TBAC module 110 may detect a token 115 indicating a change inat least one of the tokens 115 in the plurality of tokens 115. Inresponse, TBAC module 110 may communicate the token 115 and theplurality of tokens 115 to the computed risk token provider 124 torecompute the risk token 115 m in step 1630. TBAC module 110 may receivea recomputed risk token 115 m 2 in step 1640.

TBAC module 110 may begin reassigning privileges using the recomputedrisk token 115 m 2. To begin, TBAC module 110 may generate a set ofprivileges 1310 d granted to the user 112 represented by the privilegetoken 115 p in step 1650. In step 1660, TBAC module 110 may access PPP2rules 1530. In particular embodiments, TBAC module 110 may use therecomputed risk token 115 m 2 to access PPP2 rules 1530 to determinewhich privileges 1310 should be added to and removed from the set ofprivileges 1310 d. In step 1670, TBAC module 110 may determine whichprivileges 1310 in the set of privileges 1310 d should be revoked. Instep 1680, TBAC module 110 may remove the privileges 1310 from the setof privileges 1310 d that should be revoked. In step 1675, TBAC module110 may determine which privileges 1310 not in the set of privileges1310 d should be granted. In step 1685, TBAC module 110 may add theprivileges 1310 to the set of privileges 1310 d that should be granted.By adding and removing privileges 1310, TBAC module 110 will produce anew set of privileges 1310 e. TBAC module 110 may continue by generatinga new privilege token 115 p 2 representing the new set of privileges1310 e. TBAC module 110 may conclude by communicating the new privilegetoken 115 p 2 to facilitate the updating of the privileges 1310 of theuser 112.

In particular embodiments, because system 100 may detect when aprivilege 1310 should be denied while user 112 is accessing resource145, system 100 may provide a more robust and dynamic privilegingprocess. Furthermore, because TBAC module 110 uses tokens 115 toreassign privileges, system 100 may perform privilege reassignmentfaster and more efficiently.

FIGS. 17 and 18 illustrate system 100 performing packet prioritization.In general, some users 112 of system 100 may be more important thanother users 112. It may be desirable to prioritize the tasks of theimportant users 112 over the tasks of the other users 112. To accomplishthis, system 100 may prioritize packets 1725 by processing the networkpackets 1720 of the important users 112 before the network packets 1725of the other users 112. The process of determining a user 112 isimportant and prioritizing the packets of the important user 112 isreferred to as packet prioritization, which is discussed further withrespect to FIGS. 19 and 20.

TBAC module 110 may facilitate access by a user 112 to a resource 145.TBAC module 110 may determine that user 112 is a high priority user andshould have his packets processed before the packets of other users 112.TBAC module 110 may generate a token 115 to indicate that user 112 is ahigh priority user. TBAC module 110 may communicate the token 115 tofacilitate the prioritization of the packets of user 112.

FIG. 17 illustrates the system 100 of FIG. 1 prioritizing packets 1725.As provided in FIG. 17, TBAC module 110 may store a hard token 115 g(that may include a device identifier that identifies a device 114) anda compliance token 115 h to indicate that device 114 is capable ofconsuming a resource 145. In particular embodiments, TBAC module 110 mayreceive a subject token 115 k indicating the priority of user 112. As anexample and not by way of limitation, subject token 115 k may include auser identifier that indicates that user 112 is a high priority user. Inparticular embodiments, subject token 115 k may be correlated with hardtoken 115 g to associate the high priority user 112 with device 114. Asan example and not by way of limitation, correlating the hard token 115g with the subject token 115 k may indicate that the device 114 is beingused by the high priority user 112.

TBAC module 110 may use subject token 115 k to access packetprioritization (PPP1) rules 1730 stored in memory 134 to determine thepriority of user 112. As an example and not by way of limitation, aparticular PPP1 rule 1730 may specify that user 112 associated withsubject token 115 k should be prioritized above all other users 112 inthe system 100. As a result, by applying the particular PPP1 rule 1730,TBAC module 110 may determine that the user 112 associated with subjecttoken 115 k is a high priority user 112 and that packets from the highpriority user 112 should be processed before packets from any other user112 of system 100.

TBAC module 110 may generate a notification token 115 q indicating thepriority of user 112. In particular embodiments, notification token 115q may include the user identifier associated with the high priority user112 and the device identifier associated with the device 114 of the highpriority user 112. Notification token 115 q further include instructionson how to prioritize packet 1720 from user 112. As an example and not byway of limitation, if user 112 is a high priority user, notificationtoken 115 q may include instructions to prioritize packet 1720 from user112. TBAC module 110 may then communicate notification token 115 q tonetwork 120. In particular embodiments, TBAC module 110 may communicatenotification token 115 q to a network component of network 120 such as,for example, a router, a switch, a gateway, or a server such as a securetoken server. In response, network 120 may recognize packet 1720 fromuser 112 as a high priority packet 1720 and prioritize high prioritypacket 1720 over other packets 1725. As an example and not by way oflimitation, network 120 may process high priority packets 1720 before itprocesses other packets 1725 even if the other packets 1725 arrived atnetwork 120 prior to the high priority packet 1720.

In this manner, a process associated with the high priority user 112 maybe prioritized over the process of another user 112. As an example andnot by way of limitation, high priority user 112 may be authenticatedprior to other users 112 because the packets 1720 of high priority user112 are prioritized over the packets 1725 of other users 112. As anotherexample and not by way of limitation, by prioritizing packets 1720 fromhigh priority user 112, high priority user 112 may be authorized toaccess a resource 145 before other users 112 of the system 100. Althoughthis disclosure describes prioritizing particular processes of highpriority user 112, this disclosure contemplates prioritizing anysuitable process of high priority user 112. In general, TBAC module 110may communicate a session associated with the high priority user 112 tonetwork 120 such that all packets 1720 associated with the session ofthe high priority user 112 may be prioritized over the packets 1725 ofother users 112. TBAC module may further designate the session token 115j associated with the session as a high priority session token 115 j.

As yet another example and not by way of limitation, TBAC module 110 mayprioritize the provisioning of a container 210 to device 114 associatedwith the high priority user 112 by prioritizing the packets 1720 of thehigh priority user 112. TBAC module 110 may communicate a token 115 tofacilitate the provisioning of a container 210 to device 114. Container210 may include a virtual machine. If notification token 115 q indicatesthat user 112 is a high priority user, network 120 may process thepackets 1720 associated with token 115 before processing the packets1725 of other users 112 of system 100. As a result, network 120 mayfacilitate the provisioning of the container 210 to device 114 beforeprocessing other packets 1725. As an example and not by way oflimitation, if a high priority user 112 and another user 112 were bothwaiting for a container 210 to be provisioned to their devices 114,network 120 may prioritize the packets 1725 of the high priority user112 thereby resulting in the provisioning of the container 210 to thehigh priority user 112 prior to provisioning of the container 210 to theother user 112.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 17, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 17 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 17 includes all the elements of system 100in FIG. 1.

FIG. 18 is a flowchart illustrating a method 1800 of prioritizingpackets 1725 using the system 100 of FIG. 1. TBAC module 110 may performmethod 1800. As provided by FIG. 18, TBAC module 110 may begin bystoring a hard token 115 g, a compliance token 115 h, and a sessiontoken 115 j, among others, as appropriate, in step 1810. TBAC module 110may continue by receiving a subject token 115 k indicating the priorityof a user 112 in step 1820. In particular embodiments, the subject token115 k may indicate the user 112 is a high priority user. In particularembodiments, in response to the determination that the user 112 is ahigh priority user, the session token 115 j may be designated a highpriority session token. TBAC module 110 may continue by accessing PPP1rules 1730 in step 1830. In step 1840, TBAC module 110 may determine,based on PPP1 rules 1730, if the user 112 is a high priority user. Ifthe user 112 is not a high priority user, TBAC module 110 may conclude.

If the user 112 is a high priority user, TBAC module 110 may initiatepacket prioritization for the high priority user. To begin, TBAC module110 generate a notification token 115 q that includes a user identifieridentifying the high priority user and a device identifier identifying adevice 114 of the high priority user in step 1850. TBAC module 110 mayconclude in step 1860 by communicating the notification token 115 q toat least one network component to instruct the network component toprioritize packet communications associated with the high priority useror the device 114 of the high priority user.

In particular embodiments, by prioritizing the packets of certain users112, system 100 may provide more dynamic functionality to users 112.Furthermore, because TBAC module 110 uses tokens 115 to facilitatepacket prioritization, system 100 may be able to quickly and efficientlydetermine when to prioritize the packets of a certain user.

FIGS. 19 and 20 illustrate system 100 conditioning an access decision900. In some instances, making an access decision 900 may be morecomplicated than granting or denying access. There may be conditions1910 attached to those decisions. For example, a decision to deny may beaccompanied with a condition 1910 that, if satisfied, may result in thegranting of access. The process of determining conditions 1910 andcommunicating the conditions 1910 is referred to as conditioning, whichis discussed further with respect to FIGS. 19 and 20.

TBAC module 110 may make an access decision 900 following the processdiscussed with respect to FIGS. 8-10. In addition to making a decisionto grant or deny access, TBAC module 110 may determine conditionsassociated with the decision to grant or deny access. TBAC module 110may generate a decision token 115 n that represents the condition, andmay communicate the decision token 115 n to facilitate enforcement ofthe condition.

FIG. 19 illustrates the system 100 of FIG. 1 conditioning an accessdecision 900. As provided in FIG. 19, TBAC module 110 may store a hardtoken 115 g, a compliance token 115 h, a VM token 115 i, a subject token115 k, a dataset token 115 l, a risk token 115 m, and a session token115 j, among others, as appropriate. These tokens 115 may indicate auser 112 is requesting access to a resource 145 over a network 120.Using these tokens 115, TBAC module 110 may make an access decision 900following the process described with respect to FIGS. 8 through 10. Inaddition to making an access decision 900, TBAC module 110 may determinea condition 1910 associated with the access decision 900. TBAC module110 may use the stored tokens 115 to access conditioning (DDD1) rules1930 stored in memory 134 to determine the condition 1910. A particularDDD1 rule 1930 may specify a condition 1910 associated with accessing aparticular resource 145. In particular embodiments, the condition 1910may include an obligation 1920, and/or a message 1940 associated withthe access decision 900.

Condition 1910 may include an obligation 1920 to be fulfilled inconjunction with enforcing the access decision 900. In particularembodiments, obligation 1920 must be performed in conjunction withenforcing the access decision 900. As an example and not by way oflimitation, obligation 1920 may indicate that resource provider 140 mustsynchronize its system clock with the network 120 clock before grantingaccess to a resource 145. In certain embodiments, obligation 1920 may beoptional with respect to enforcing the access decision 900. As anexample and not by way of limitation, obligation 1920 may recommend thatresource provider 140 may synchronize its system clock with the network120 clock before granting access to a resource 145.

Obligation 1920 may indicate a task to be performed by a component ofsystem 100 upon receiving the access decision 900 along with theobligation 1920. As an example and not by way of limitation, obligation1920 may be synchronizing a system clock of the resource provider 140with a clock on a network 120. Upon receiving the access decision 900along with the obligation 1920 to synchronize a system clock, resourceprovider 140 may enforce the access decision 900 and synchronize itssystem clock with a clock on network 120. As another example and not byway of limitation, obligation 1920 may be initializing the logging oferrors and performance metrics related with enforcing the accessdecision 900. Upon receiving the access decision 900 along with theobligation 1920, resource provider 140 may enforce the access decision900 and initialize the logging of errors and performance metrics relatedwith enforcing the access decision. As yet another example and not byway of limitation, obligation 1920 may be tracking transactions overnetwork 120. Upon receiving the access decision 900 along with theobligation 1920, resource provider 140 may enforce the access decision900 and begin tracking transactions associated with a requested resource145.

Obligation 1920 may indicate a task to be performed by user 112 beforeaccess to the resource 145 may be granted. As an example and not by wayof limitation, obligation 1920 may indicate that a peripheral devicesuch as a USB drive is attached to device 114 and that the peripheraldevice should be removed before access may be granted to resource 145.During enforcement of an access decision 900, user 112 may be notifiedto remove the peripheral device. If user 112 removes the peripheraldevice from device 114, obligation 1920 may be satisfied and access toresource 145 may be granted to user 112. As another example, and not byway of limitation, obligation 1920 may indicate that informationrequired to access resource 145 such as, for example, the birthday ofthe user 112 may be missing. If user 112 supplies the missinginformation, for example by entering the birthday into device 114,obligation 1920 may be satisfied and access to resource 145 may begranted.

Condition 1910 may include a message 1940. Message 1940 may provide anexplanation for the access decision 900. As an example and not by way oflimitation, if access to resource 145 was denied because user 112 wasnot of a particular age, message 1940 may state that access was deniedbecause user 112 was not old enough. As another example and not by wayof limitation, if access to resource 145 was granted because user 112was exempt from an age restriction, message 1940 may state that accesswas granted because user 112 is exempt from the age restriction. Message1940 may further provide instructions on how to fulfill obligation 1920.For example, if obligation 1920 indicates that user 112 should remove aUSB drive attached to device 114 before access may be granted, message1940 may instruct user 112 to remove the USB drive.

In particular embodiments, TBAC module 110 may generate a decision token115 n representing condition 1910. In certain embodiments, decisiontoken 115 n may also represent the access decision 900. TBAC module 110may communicate decision token 115 n to resource provider 140 tofacilitate the enforcement of the access decision 900 and the condition1910.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 19, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 19 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 19 includes all the elements of system 100in FIG. 1.

FIG. 20 is a flowchart illustrating a method 2000 of conditioning accessdecisions 900 using the system 100 of FIG. 1. TBAC module 110 mayperform method 2000. As provided in FIG. 20, TBAC module 110 may beginby storing a hard token 115 g, compliance token 115 h, VM token 115 i,subject token 115 k, risk token 115 m, and session token 115 j, amongothers, as appropriate, as a plurality of tokens in step 2010. TBACmodule 110 may continue by accessing DDD1 rules 1930 in step 2020. Instep 2030, TBAC module 110 may determine if there is a condition 1910associated with the plurality of tokens. If there is no condition 1910associated with the plurality of tokens, TBAC module 110 may conclude.

If there is a condition 1910 associated with the plurality of tokens,TBAC module 110 may initiate conditioning. To begin, TBAC module 110 maycontinue to steps 2040 and 2042. In step 2040, TBAC module 110 maydetermine if the condition 1910 includes an obligation 1920. If thecondition 1910 does include an obligation 1920, TBAC module 110 maycontinue to step 2050 to indicate the obligation 1920 should be includedin a decision token 115 n. In step 2042, TBAC module 110 may determineif the condition 1910 includes a message 1940. If the condition 1910includes a message 1940, TBAC module 110 may continue to step 2052 toindicate the message 1940 should be included in a decision token 115 n.TBAC module 110 may continue to step 2060 to generate the decision token115 n with the obligation 1920 and/or message 1940 if they are indicatedto be included in the decision token 115 n. TBAC module 110 may concludein step 2070 by communicating the decision token 115 n.

In particular embodiments, because system 100 may place conditions onaccess decisions 900, system 100 may make more robust access decisions900. Furthermore, because TBAC module 100 uses tokens to performconditioning, system 100 may make an access decision 900 quicker andmore efficiently.

FIGS. 21 and 22 illustrate the system 100 accessing related resources145 b. In general, certain resources 145 may share a relationship withsome related resources 145 b. For example, a computer resource mayinclude several sub-resources such as an email client, a word processor,and a browser. When system 100 determines whether a user 112 may accessa resource 145, system 100 may also determine, based on access to theresource 145, whether there are any related resources 145 b that user112 may also access. This process of determining access to relatedresources 145 b is discussed further with respect to FIGS. 21 and 22.

TBAC module 110 may make an access decision 900 for a resource 145following the process discussed with respect to FIGS. 8-10. TBAC module110 may also make an access decision 900 for any related resources 145 bthat share a relationship with the resource 145. For example, user 112may frequently access the related resource 145 b while the user 112accesses the resource 145. TBAC module 110 may provide the user 112 witha better and more seamless user experience by determining access to therelated resource 145 b based on the access decision 900 for the resource145.

FIG. 21 illustrates the system 100 of FIG. 1 making an access decision900 for a related resource 145 b. As provided in FIG. 21, TBAC module110 may store hard token 115 g, compliance token 115 h, VM token 115 i,subject token 115 k, resource token 115 c, risk token 115 m, and sessiontoken 115 j, among others, as appropriate. These tokens 115 may indicatethat a user 112 is attempting to access a resource 145. TBAC module 110may use these tokens 115 to make an access decision 900 following theprocess described with respect to FIGS. 8-10. In particular embodiments,while making the access decision 900, TBAC module 110 may determine anauthorization level 2110 associated with access by the user 112 to theresource 145. The authorization level 2110 may be a numerical value. Ifthe value of authorization level 2110 is above a certain threshold, thenuser 112 may be granted access to resource 145. In particularembodiments, TBAC module 110 may use the authorization level 2110 todetermine if user 112 may be granted access to any related resources 145b that share a relationship with resource 145.

To accomplish this, TBAC module 110 may use authorization level 2110 toaccess resource relationship (RRR3) rules 2130 stored in memory 134.RRR3 rules 2130 may specify a related resource 145 b that shares arelationship with the resource 145. As an example and not by way oflimitation, a particular RRR3 rule 2130 may specify that resource 145 isa composite resource that includes several sub-resources, and relatedresource 145 b may be a sub-resource of resource 145. As another exampleand not by way of limitation, a particular RRR3 rule 2130 may specifythat related resource 145 b is a frequently accessed resource inconjunction with accessing resource 145. Although this disclosuredescribes related resource 145 b sharing particular relationships withresource 145, this disclosure contemplates related resource 145 bsharing any suitable relationship with resource 145. Based onauthorization level 2110, TBAC module 110 may determine that user 112 isauthorized to access related resource 145 b. As an example and not byway of limitation, TBAC module 110 may determine that the authorizationlevel 2210 is an 8. If an authorization level 2110 of at least 7 isrequired to access the related resource 145 b, then TBAC module 110 maygrant access to the related resource 145. As another example and not byway of limitation, if resource 145 includes several sub-resources, oneof which is related resource 145 b, an authorization level 2210 of an 8may be sufficient to access the related resource 145 b, but it may notbe sufficient to access other sub-resources of resource 145. In thatcase, user 112 may be granted access to related resource 145 b, butother sub-resources may be hidden or inaccessible.

In particular embodiments, TBAC module 110 may generate a decision token115 n representing the determination that user 112 is authorized toaccess related resource 145 b. TBAC module 110 may communicate decisiontoken 115 n to resource provider 140 to facilitate enforcement of thedecision to grant access to the related resource 145 b. In response,resource provider 140 may grant user 112 access to related resource 145b. In particular embodiments, TBAC module 110 may further receive arecomputed risk token 115 m 2 representing the risk associated withgranting the user 112 access to the resource 145 and the relatedresource 145 b. Recomputed risk token 115 m 2 may be computed based onaccess by the user 112 to resource 145 and related resource 145 b, notjust resource 145.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 21, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 21 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 21 includes all the elements of system 100in FIG. 1.

FIG. 22 is a flowchart illustrating a method 2200 of making an accessdecision 900 for a related resource 145 b using the system 100 ofFIG. 1. TBAC module 110 may perform method 2200. As provided in FIG. 22,TBAC module 110 may begin by storing a hard token 115 g, compliancetoken 115 h, VM token 115 i, subject token 115 k, resource token 115 c,risk token 115 m, and session token 115 j, among others as appropriateas a plurality of tokens in step 2210. TBAC module 110 may continue bystoring an authorization level 2110 associated with access by a user 112to a resource 145 in step 2220. In particular embodiments, if theauthorization level 2110 is above a certain threshold then user 112 maybe granted access to the resource 145. TBAC module 110 may continue byaccessing RRR3 rules 2130 in step 2230. In step 2240, method 2200 maydetermine, based on RRR3 rule 2130, if there is a related resource 145 bthat shares a relationship with the resource 145. If there is no relatedresource 145 b, TBAC module 110 may conclude. If there is a relatedresource 145 b, TBAC module 110 may continue to step 2250 to determineif the user 112 is authorized to access the related resource 145 b basedon the authorization level 2110. If the user is not authorized to accessthe related resource, TBAC module 110 may conclude. If the user 112 isauthorized to access the related resource 145 b, TBAC module 110 maycontinue to step 2260 to generate a decision token 115 n indicating thatuser 112 should be granted access to the related resource 145 b. TBACmodule 110 may then conclude at step 2270 by communicating the decisiontoken 115 n to facilitate access to the related resource 145 b.

In particular embodiments, because system 100 may determine access torelated resources 145 b, system 100 may provide a more seamless userexperience for a user 112. Furthermore, because TBAC module 110 usestokens to determine access to the related resources 145 b, system 100may determine access to the related resources 145 b quicker and moreefficiently.

FIGS. 23 and 24 illustrate the system 100 performing a real-time riskupdate. In general, changes may occur in the system 100 while a user 112is accessing a resource 145. These changes may pose risks, such assecurity risks, for the system 100, and access to the resource 145 maybe cut off because of these risks. The process of detecting a change anddetermining the risk posed by the change is referred to as real-timerisk updating, which is discussed further with respect to FIGS. 23 and24.

TBAC module 110 may detect changes in system 100 while monitoring asession and determine whether those changes trigger a real-time riskupdate. If a change does trigger a real-time risk update, TBAC module110 may request a real-time risk update in the form of a recomputed risktoken 115 m 2. TBAC module 110 may then use the recomputed risk token115 m 2 to make an access decision 900 following the process describedwith respect to FIGS. 8-10.

FIG. 23 illustrates the system 100 of FIG. 1 updating risk in real-time.As provided in FIG. 23, TBAC module 110 may store a hard token 115 g, asubject token 115 k, a resource token 115 c, a network token 115 f, arisk token 115 m, and a session token 115 j, among others asappropriate, as a plurality of tokens. The plurality of tokens mayindicate a user 112 is accessing a resource 145 over network 120. TBACmodule 110 may receive a token 115 that indicates a change associatedwith accessing a resource 145. In particular embodiments, token 115 mayfurther indicate that a change has occurred to at least one token 115 inthe plurality of tokens. In response to receiving token 115, TBAC module110 may use token 115 and/or the plurality of tokens to access real-timerisk (RRR2) rules 2330 stored in memory 134. In particular embodiments,RRR2 rules 2330 may specify which changes indicated by token 115 maytrigger a risk update. As an example and not by way of limitation, aparticular RRR2 rule 2330 may specify that jitter over network 120 maytrigger a risk update. If token 115 indicates that network 120 isexperiencing jitter, then token 115 may trigger a risk update.

To initiate the risk update, TBAC module 110 may generate a new datasettoken 115 l 2 that represents the token 115 and the plurality of tokens.As an example and not by way of limitation, if token 115 is a networktoken 115 f indicating that network 120 is experiencing jitter, then newdataset token 115 l 2 may indicate the presence of the network token 115f indicating jitter over the network 120. New dataset token 115 l 2 mayfurther indicate the presence of the tokens 115 in the plurality oftokens. For example, new dataset token 115 l 2 may also indicate thepresence of risk token 115 m, which represents a risk associated withaccessing the resource before the change. In this manner, new datasettoken 115 l 2 may represent both the state of system 100 prior to thechange and the change itself.

TBAC module 110 may communicate the new dataset token 115 l 2 to thecomputed risk token provider 124. In response, computed risk tokenprovider 124 may include the change indicated by token 115 inrecomputing the risk represented by risk token 115 m. In this manner,the recomputed risk may represents the risk associated with continuingaccess to the resource with the change. After recomputing the risk,computed risk token provider 124 may generate a recomputed risk token115 m 2 that represents the recomputed risk. In particular embodiments,computed risk token provider 124 may communicate the recomputed risktoken 115 m 2 to TBAC module 110. In response, TBAC module 110 mayincorporate recomputed risk token 115 m 2 into the plurality of tokens.As an example and not by way of limitation, TBAC module 110 may replacerisk token 115 m with recomputed risk token 115 m 2. As another exampleand not by way of limitation, TBAC module 110 may include recomputedrisk token 115 m 2 into the plurality of tokens in addition to the risktoken 115 m.

In particular embodiments, the recomputed risk represented by recomputedrisk token 115 m 2 may affect an access decision 900 previously made byTBAC module 110 following the process discussed with respect to FIGS.8-10. In that case, TBAC module 110 may perform that process again withthe recomputed risk token 115 m 2 to produce a new access decision 900.In particular embodiments, TBAC module 110 may generate a decision token115 n that represents the new access decision 900. TBAC module 110 maythen communicate decision token 115 n to facilitate enforcement of thenew access decision 900. In particular embodiments, TBAC module 110 maycommunicate the decision token 115 n to the resource provider 140.

Although this disclosure describes TBAC module 110 and computed risktoken provider 124 performing certain actions with respect to FIG. 23,this disclosure contemplates the processor 132 and the memory 134 of theTBAC module 110 and the processor 132 of the computed risk tokenprovider 124 performing these actions. The illustration of system 100 inFIG. 23 does not specifically illustrate all of the elements from theillustration of system 100 in FIG. 1 so that particular aspects ofsystem 100 may be emphasized. However, system 100 of FIG. 23 includesall the elements of system 100 in FIG. 1.

FIG. 24 is a flowchart illustrating a method 2400 of updating risk inreal time using the system 100 of FIG. 1. TBAC module 110 may performmethod 2400. As provided by FIG. 24, TBAC module 110 may begin bystoring a hard token 115 g, subject token 115 k, resource token 115 c,network token 115 f, risk token 115 m, and session token 115 j, amongothers as appropriate, as a plurality of tokens in step 2410. TBACmodule 110 may continue by receiving a token 115 indicating a changeassociated with accessing a resource 145 in step 2420. In particularembodiments, the change may correspond with a change to a token 115 inthe plurality of tokens. TBAC module 110 may continue by accessing RRR2rules 2330 in step 2430. In step 2440, TBAC module 110 may determine ifthe change triggers a risk update. If the change does not trigger a riskupdate, TBAC module 110 may conclude.

If the change does trigger a risk update, TBAC module 110 may initiatethe risk updating process. To begin, TBAC module 110 may generate a newdataset token 115 l 2 that represents the plurality of tokens and thetoken 115 that indicates the change in step 2450. In particularembodiments, new dataset token 115 l 2 may indicate the state of system100 prior to the change and the change itself by representing theplurality of tokens and the token 115 that indicates the change. TBACmodule 110 may continue to communicate the new dataset token 115 l 2 tothe computed risk token provider 124 in step 2460. In response, computedrisk token provider 124 may include the change represented by the token115 in recomputing the risk represented by risk token 115 m and generatea recomputed risk token 115 m 2 that represents the recomputed risk. Instep 2470, TBAC module 110 may receive the recomputed risk token 115 m2.

In particular embodiments, TBAC module 110 may continue to step 2480 toupdate an access decision 900 based on the recomputed risk token 115 m2. TBAC module 110 may update the access decision 900 following theprocess discussed with respect to FIGS. 8-10. In step 2485, TBAC module110 may generate a decision token 115 n that represents the updatedaccess decision 900. TBAC module 110 may conclude at step 2490 bycommunicating the decision token 115 n to facilitate enforcement of theupdated access decision 900.

In particular embodiments, because system 100 may perform real-time riskupdates, system 100 may provide better security associated withaccessing a resource 145. Furthermore, because TBAC module 110 usestokens 115 to perform the real-time risk update, system 100 may providefaster and more efficient security.

FIGS. 25 and 26 illustrate the system 100 combining risk ratings. Ingeneral, during any session, a user 112 may perform severaltransactions. A particular transaction may have a risk associated withit that is different from the risk associated with another transaction.System 100 may determine if these risks are related and combine them togenerate a clearer picture of the overall risk posed by user 112. Thisprocess of determining related risks and combining them is referred toas combining risk ratings, which is discussed further with respect toFIGS. 25 and 26.

TBAC module 110 may store multiple risk tokens 115 m while monitoring asession. Each risk token 115 m may represent a risk associated with aparticular transaction. TBAC module 110 may determine which risks arerelated and combine the related risks into a composite risk token 115 m3. TBAC module 110 may then use the composite risk token 115 m 3 to makean access decision 900 following the process described with respect toFIGS. 8-10.

FIG. 25 illustrates the system 100 of FIG. 1 combining risk ratings. Asprovided by FIG. 25, TBAC module 110 may store a hard token 115 g, asubject token 115 k, a resource token 115 c, a first risk token 115 m 4,a second risk token 115 m 5, a third risk token 115 m 6, and a sessiontoken 115 j, among others as appropriate as a plurality of tokens. Inparticular embodiments, first risk token 115 m 4, second risk token 115m 5, and third risk token 115 m 6 may each represent a risk rating. Therisk rating may be a numerical value that indicates a risk associatedwith granting a particular user 112 access to a particular resource 145.Although this disclosure describes a particular number of risk tokens115 m stored in TBAC module 110, this disclosure contemplates any numberof risk tokens 115 m stored in TBAC module 110.

In particular embodiments, particular combinations of the risk ratingsrepresented by first risk token 115 m 4, second risk token 115 m 5,and/or third risk token 115 m 6 may provide more information about therisk associated with user 112 145. To determine these particularcombinations, TBAC module 110 may use the first risk token 115 m 4, thesecond risk token 115 m 5, and the third risk token 115 m 6 to accessrisk combination (CCC3) rules 2530 stored in memory 134. In particularembodiments, a particular CCC3 rule 2530 may specify which risk tokens115 m may be related, and therefore may be combined to yield informationabout risk. As an example and not by way of limitation, the particularCCC3 rule 2530 may specify that the second risk token 115 m 5 and thethird risk token 115 m 6 are related because they are associated withsub-resources 145 b of a composite resource 145, and that therefore, thecombination of the second risk token 115 m 5 and the third risk token115 m 6 may yield information about the risk associated with grantingaccess to another sub-resource 145 b of the composite resource 145.Although this disclosure describes risk tokens 115 m being related byresource 145, this disclosure contemplates risk tokens 115 m beingrelated in any suitable manner, including by user 112, network 120, anaction performed by user 112, or any combination thereof. For example, aparticular CCC3 rule 2530 may specify that first risk token 115 m 4 andthe second risk token 115 m 5 are related because they are associatedwith similar actions performed by user 112, such as for example,withdrawals from particular accounts of user 112, and that therefore,the combination of the first risk token 115 m 4 and the second risktoken 115 m 5 may yield information about the risk associated withgranting a withdrawal to user 112 for another account.

In particular embodiments, the particular CCC3 rule 2530 may furtherspecify how to combine risk ratings. As an example and not by way oflimitation, the particular CCC3 rule 2530 may specify that the riskrating represented by second risk token 115 m 5 and the risk ratingrepresented by third risk token 115 m 6 should be arithmeticallycombined by a weighted average to produce a composite risk rating. Inresponse, TBAC module 110 may produce a composite risk rating bycomputing the weighted average, indicated by the particular CCC3 rule2530, of the risk ratings represented by second risk token 115 m 5 andthird risk token 115 m 6. TBAC module 110 may then generate a compositerisk token 115 m 3 that represents the composite risk rating. Althoughthis disclosure describes combining risk ratings in a particular manner,this disclosure contemplates combining the risk ratings in any suitablemanner.

In particular embodiments, TBAC module 110 may use the composite risktoken 115 m 3 to facilitate the making of an access decision 900following the process discussed with respect to FIGS. 8-10. As anexample and not by way of limitation, if composite risk token 115 m 3was computed from risk tokens 115 m associated with differentsub-resources 145 b of a composite resource, TBAC module 110 may usecomposite risk token 115 m 3 to facilitate the making of an accessdecision 900 associated with access to another sub-resource 145 b of thecomposite resource 145. As another example and not by way of limitation,if composite risk token 115 m 3 was computed from risk tokens 115 massociated with a similar action, such as for example, a withdrawal fromdifferent accounts, TBAC module 110 may use composite risk token 115 m 3to facilitate the making of an access decision 900 associated with theaction, such as for example, a withdrawal from another account.

After making the access decision 900, TBAC module 110 may generate adecision token 115 n that represents the access decision 900. TBACmodule 110 may then communicate the decision token 115 n to facilitateenforcement of the access decision 900. In particular embodiments, TBACmodule 110 may communicate the decision token 115 n to the resourceprovider 140 to facilitate enforcement of the access decision 900.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 25, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 25 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 25 includes all the elements of system 100in FIG. 1.

FIG. 26 is a flowchart illustrating a method 2600 of combining riskratings using the system 100 of FIG. 1. TBAC module 110 may performmethod 2600. As provided by FIG. 26, TBAC module 110 may begin bystoring a plurality of risk tokens 115 m in step 2610. TBAC module 110may continue by accessing CCC3 rules 2530 in step 2620. In step 2630,TBAC module 110 may determine, based on CCC3 rules 2530, if there is aset of risk tokens 115 m in the plurality of risk tokens 115 m that arerelated according to the process described above with respect to FIG.25. If there is not a set of related risk tokens 115 m, TBAC module 110may conclude.

If there is a set of related risk tokens 115 m, TBAC module 110 maycombine risk ratings. To begin, TBAC module 110 may arithmeticallycombine the risk ratings represented by each risk token 115 m in the setof related risk tokens 115 m to produce a composite risk rating in step2640. As an example and not by way of limitation, TBAC module 110 maycompute a weighted average of the risk ratings. TBAC module 110 maycontinue to generate a composite risk token 115 m 2 representing thecomposite risk rating in step 2650. In step 2660, TBAC module 110 mayuse the composite risk token 115 m 2 to facilitate the making of anaccess decision 900 following the process discussed with respect toFIGS. 8-10. TBAC module 110 may continue in step 2670 by generating adecision token 115 n representing the access decision 900. TBAC module110 may conclude by communicating the decision token 115 n to facilitateenforcement of the access decision 900 in step 2680.

In particular embodiments, because system 100 may combine risk ratings,system 100 may make more robust access decisions 900. Furthermore,because TBAC module 110 uses tokens 115 to combine risk ratings, system100 may generate an overall risk for a user 112 quicker and moreefficiently.

FIGS. 27 and 28 illustrate the system 100 tagging transactions 2710. Ingeneral, even a very trusted user 112 using a very secure network 120and device 114 may sometimes perform a risky transaction 2710. In thosesituations, despite the security credentials of the user 112, it may bedesirable to flag the transaction 2710 and monitor it closely. Theprocess of determining when a transaction 2710 is risky and flagging andmonitoring the transaction 2710 is referred to as transaction tagging,which is discussed further with respect to FIGS. 27 and 28.

TBAC module 110 may be monitoring a session that facilitates access by auser 112 to a resource 145 when TBAC module 110 detects the user 112 isattempting to perform a transaction 2710 that is risky. In response,TBAC module 110 may generate a tag 2720 that is added to the transaction2710 and/or the tokens 115 associated with user 112. TBAC module 110 mayfurther generate a message 2740 that indicates the transaction should beprocessed in isolation.

FIG. 27 illustrates the system 100 of FIG. 1 tagging transactions 2710.As provided in FIG. 27, TBAC module 110 may store a hard token 115 g, asubject token 115 k, a resource token 115 c, a network token 115 f, asession token 115 j, and others as appropriate. Session token 115 j maybe associated with a session. In particular embodiments, the session mayfacilitate the processing of a transaction 2710. The transaction mayrepresent an action taken by a user 112 against a resource 145. As anexample and not by way of limitation, transaction 2710 may be a transferof money from a domestic bank account to a foreign bank account. Inparticular embodiments, user 112 may attempt to perform the transaction2710. As a result, TBAC module 110 may receive a transaction risk token115 r associated with the transaction 2710. Transaction risk token 115 rmay indicate a risk associated with processing the transaction 2710. Asan example and not by way of limitation, if transaction 2710 representsan attempt to transfer money from a domestic bank account to a foreignbank account, transaction risk token 115 r may indicate that transaction2710 is a high risk transaction because of the potential for moneylaundering or tax evasion.

TBAC module 110 may use transaction 2710 and transaction risk token 115r to access transaction tagging (TTT4) rules 2730 stored in memory 134.In particular embodiments, TTT4 rules 2730 may specify when atransaction 2710 may be classified as a high risk transaction based ontransaction risk token 115 r. TBAC module 110 may use TTT4 rules 2730 todetermine if a particular transaction 2710 is a high risk transaction.If the particular transaction 2710 is a high risk transaction, TBACmodule 110 may initiate the transaction tagging process.

In particular embodiments, TBAC module 110 may initiate the transactiontagging process by generating a tag 2720. Tag 2720 may be added totransaction 2710 to indicate that the transaction 2710 is a high risktransaction. As an example and not by way of limitation, tag 2720 may bea ciphered value added to the syntax of the transaction 2710. Tag 2720may also be added to a subject token 115 k associated with user 112 or aresource token 115 c associated with resource 145. In particularembodiments, tag 2720 may facilitate tracing of the transaction 2710. Asan example and not by way of limitation, after tag 2720 has been addedto transaction 2710, tag 2720 may act as a unique flag that identifiestransaction 2710 wherever it may be processed. By following where tag2720 appears, transaction 2710 may be traced at each step of itsprocessing. By tracing the transaction 2710, it may be possible toremember and even recreate the steps taken to process transaction 2710.In particular embodiments, system 100 may further log the transaction2710 in a database as it is being traced during processing.

In particular embodiments, if transaction 2710 is tagged as a high risktransaction, TBAC module 110 may generate a message 2740 that indicatesthat transaction 2710 should be processed in isolation. By isolatingtransaction 2710 as it is processed, it may be easier to tracetransaction 2710 as it is processed. Message 2740 may indicate aprocessing unit 2750 that is isolated and capable of processingtransaction 2710. As an example and not by way of limitation, message2740 may indicate the location of an isolated server to whichtransaction 2710 may be sent for isolated processing. In particularembodiments, TBAC module 110 may communicate message 2740 to resourceprovider 140 to facilitate the transfer of transaction 2710 to anisolated processing unit 2750.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 27, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 27 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 27 includes all the elements of system 100in FIG. 1.

FIG. 28 is a flowchart illustrating a method 2800 of taggingtransactions 2710 using the system 100 of FIG. 1. TBAC module 110 mayperform method 2800. As provided by FIG. 28, TBAC module 110 may beginby storing a session token 115 j associated with a session thatfacilitates the processing of transactions 2710 in step 2810. In step2820, TBAC module 110 may receive a transaction 2710 associated with thesession. TBAC module 110 may continue by receiving a transaction risktoken 115 r associated with the transaction 2710 in step 2830. TBACmodule 110 may continue by accessing TTT4 rules 2730 in step 2840. Instep 2850, TBAC module 110 may determine, based on TTT4 rules 2730, ifthe transaction 2710 is a high risk transaction. If the transaction isnot a high risk transaction, TBAC module 110 may conclude.

If the transaction 2710 is a high risk transaction, TBAC module 110 mayinitiate the transaction tagging process. To begin, TBAC module 110 maygenerate a tag 2720 for the transaction 2710 in step 2860. TBAC module110 may continue by adding the tag 2720 to the transaction 2710 in step2870. In particular embodiments, the tag 2720 may facilitate the tracingof the transaction 2710 as it is processed. In step 2880 TBAC module 110may generate a message 2740 indicating the transaction 2710 should beprocessed in isolation. TBAC module 110 may conclude by communicatingthe message 2740 to facilitate the isolated processing of thetransaction 270 in step 2890.

In particular embodiments, because system 100 may tag transactions 2710,system 100 may provide a more robust security system. Furthermore,because TBAC module 110 may use tokens 115 to tag transactions 2710,system 100 may securely process transactions 2710 quicker and moreefficiently.

FIGS. 29 and 30 illustrate the system 100 performing context caching. Ingeneral, a token provider may retrieve attributes 425 from acorresponding repository 420 a-d and cache those attributes 425 in anattribute cache 2910. If the cache 2910 fills up, subsequently retrievedattributes 425 will need to replace old attributes 425 o in the cache.The process of determining which attributes 425 are old and replacingthe old attributes 425 o with new attributes 425 n is referred to ascontext caching, which is discussed further with respect to FIGS. 29 and30.

Computed risk token provider 124 may contain an attribute cache 2910.Each time the computed risk token provider 124 computes a risk token 115m, it may retrieve attributes 425 from the risk repository 420 d, andcache those attributes 425 in the attribute cache 2910. To avoid fillingup the attribute cache 2910, the computed risk token provider 124 maydetermine, based on a received dataset token 115 l, which cachedattributes 425 are old and remove them from the attribute cache 2910.Although this disclosure describes context caching using the computedrisk token provider 124, this disclosure contemplates context cachingtaking place in any suitable token provider.

FIG. 29 illustrates the system 100 of FIG. 1 performing context caching.As provided by FIG. 29, TBAC module 110 may be requesting computed risktoken provider 124 to compute or recompute a risk token 115 m. As anexample and not by way of limitation, TBAC module 110 may be performingthe real-time risk updating function discussed with respect to FIGS. 23and 24. Although this disclosure describes TBAC module 110 performing aspecific function involving the computed risk token provider 124, thisdisclosure contemplates TBAC module 110 performing any suitable functionthat involves computed risk token provider 124. As discussed withrespect to FIGS. 23 and 24, TBAC module 110 may receive a token 115 thatindicates a change that occurred during a session. TBAC module 110 maygenerate a new dataset token 115 l 2 and communicate the new datasettoken 115 l 2 to the computed risk token provider 124. The new datasettoken 115 l 2 may indicate a risk token 115 m should be computed orrecomputed.

In particular embodiments, computed risk token provider 124 may includean attribute cache 2910. Attribute cache 2910 may cache attributes 425used in previous computations of a risk token 115 m. Cached attributes2940 c may be used during subsequent computations of risk token 115 m sothat computed risk token provider 124 does not have to retrieve thecached attributes 2940 c from a risk repository 420 d. When computedrisk token provider 124 computes a risk token 115 m, computed risk tokenprovider 124 may update attribute cache 2910 by removing old attributes425 o from and by adding new attributes 425 n to attribute cache 2910.

To determine the old attributes 425 o in attribute cache 2910, computedrisk token provider 124 may examine a token 115 received from TBACmodule 110. As an example and not by way of limitation, computed risktoken provider 124 may receive a new dataset token 115 l 2 from TBACmodule 110. New dataset token 115 l 2 may indicate a set of attributes2940 a required to compute or recompute a risk token 115 m. New datasettoken 115 l 2 may further include instructions on how to compute orrecompute risk token 115 m that may facilitate the updating of attributecache 2910. Based on the indicated set of attributes 2940 a and theinstructions, computed risk token provider 124 may determine whichcached attributes 2940 c are not used in computing or recomputing therisk tokens 115 m. Computed risk token provider 124 may then mark theseattributes 425 as old. In particular embodiments, computed risk tokenprovider 124 may consider old attributes 425 o as forming an obsoleteportion of the attribute cache 2910 and may remove the old attributes425 o from the attribute cache 210. In this manner, computed risk tokenprovider 124 may ensure that attribute cache 2910 contains onlyattributes 425 that are in the set of attributes 2940 a required tocompute or recompute risk token 115 m.

Computed risk token provider 124 may add new attributes 425 n byretrieving them from risk repository 420 d and adding them to attributecache 2910. Computed risk token provider 124 may determine whichattributes 425 to retrieve from risk repository 420 d by examining theset of attributes 2940 a required to compute or recompute risk token 115m and the set of attributes 2940 b cached within attribute cache 2910after the old attributes 425 o have been removed. By examining the setof attributes 2940 a and the set of attributes 2940 b, computed risktoken provider 124 may determine that attributes 425 that are in the setof attributes 2940 a but not in the set of attributes 2940 b. Thesedetermined attributes 425 are the new attributes 425 n.

Computed risk token provider 124 may then retrieve the new attributes425 n from risk repository 420 d and add the new attributes 425 n toattribute cache 2910. In particular embodiments, computed risk tokenprovider 124 may then use the attributes 425 cached within attributecache 2910 to compute or recompute risk token 115 m. As an example andnot by way of limitation, computed risk token provider 124 may use theattributes 425 cached within attribute cache 2910 to generate arecomputed risk token 115 m 2 and communicate the recomputed risk token115 m 2 to TBAC module 110.

Although this disclosure describes TBAC module 110 and computed risktoken provider 124 performing certain actions with respect to FIG. 29,this disclosure contemplates the processor 132 and the memory 134 of theTBAC module 110 and the processor 132 of the computed risk tokenprovider 124 performing these actions. The illustration of system 100 inFIG. 29 does not specifically illustrate all of the elements from theillustration of system 100 in FIG. 1 so that particular aspects ofsystem 100 may be emphasized. However, system 100 of FIG. 29 includesall the elements of system 100 in FIG. 1.

FIG. 30 is a flowchart illustrating a method 3000 of performing contextcaching using the system 100 of FIG. 1. In particular embodiments,computed risk token provider 124 may perform TBAC module 110. Asprovided in FIG. 30, computed risk token provider 124 may begin byreceiving a dataset token 115 l indicating a change that occurred duringa session in step 3010. Computed risk token provider 124 may continue bydetermining a set of attributes 2940 a required to recompute a risktoken 115 m in step 3020. In step 3030, computed risk token provider 124may determine a set of cached attributes 2940 c in an attribute cache2910.

To free up space in the attribute cache 2910, the old attributes 425 oin the set of cached attributes 2940 c may be removed. To do so,computed risk token provider 124 may continue by examining a cachedattribute 425 in the set of cached attributes 2940 c in step 3040. Instep 3050, computed risk token provider 124 may determine if the cachedattribute 425 is in the set of attributes 2940 a required to recomputethe risk token 115 m. If the cached attribute 425 is in the set ofattributes 2940 a, then computed risk token provider 124 may leave thecached attribute 425 in the attribute cache 2910. If the cachedattribute 425 is not in the set of attributes 2940 a, computed risktoken provider 124 may remove the cached attribute 425 from theattribute cache 2910 in step 3060.

Computed risk token provider 124 may then continue to step 3070 todetermine if all cached attributes 425 in the set of cached attributes2940 c have been examined. If not, computed risk token provider 124 mayreturn to step 3040 to examine another cached attribute 425. If allcached attributes 425 have been examined, computed risk token provider124 may be sure that attribute cache 2910 contains only the set ofattributes 2940 b.

Before recomputing a risk token 115 m, computed risk token provider 124may retrieve the new attributes 425 n from the risk repository 420 d. Toaccomplish this, computed risk token provider 124 may determine the newattributes 425 n by examining the set of attributes 2940 a required torecompute the risk token 115 m and the set of cached attributes 2940 bin step 3075. The new attributes 425 n will be the attributes in the setof attributes 2940 a but not in the set of cached attributes 2940 b.Computed risk token provider 124 may continue to step 3080 by retrievingthe new attributes 425 n. In step 3090, computed risk token provider 124may cache the retrieved attributes 425 n in the attribute cache 2910.Computed risk token provider 124 may then conclude by recomputing therisk token 115 m using cached attributes 425 in the attribute cache 2910in step 3095.

In particular embodiments, because system 100 may perform contextcaching, system 100 may provide more efficient caching of attributes425. Furthermore, because system 100 uses tokens 115 to perform contextcaching, system 100 may make faster determinations regarding whichattributes 425 to remove from the attribute cache 2910.

FIGS. 31 and 32 illustrate the system 100 recycling a virtual machine3110 b. In general, user 112 may consume a resource 145 through avirtual machine 3110 b provisioned to device 114. Over time, virtualmachine 3110 b may need to be recycled, sometimes frequently. System 100may determine when a particular virtual machine 3110 b needs to berecycled and recycle the virtual machine 3110 b accordingly. Thisrecycling process is discussed further with respect to FIGS. 31 and 32.

TBAC module 110 may monitor virtual machine 3110 b through a timestamp3120 and a time threshold 3125. When TBAC module 110 determines, basedon the timestamp 3120 and the time threshold 3125, that the virtualmachine 3110 b is stale, TBAC module 110 may generate a recycle token tofacilitate the recycling of the virtual machine 3110 b.

FIG. 31 illustrates the system 100 of FIG. 1 performing virtual machinerecycling. As provided by FIG. 31, device 114 may have been provisionedwith container 210. Container 210 may include a virtual machine 3110 bexecuting a process 3140. Virtual machine 3110 b may be executingprocess 3140 on device 114. TBAC module 110 may store a hard token 115g, a compliance token 115 h, a VM token 115 i, a subject token 115 k, aresource token 115 c, a risk token 115 m, and a session token 115 j,among others as appropriate. The VM token 115 i may representinformation associated with virtual machine 3110 b. In particularembodiments, VM token 115 i may include a timestamp 3120 associated withvirtual machine 3110 b and a time threshold 3125 associated with virtualmachine 3110 b. Timestamp 3120 may indicate the time at which virtualmachine 3110 b was established. Time threshold 3125 may indicate anamount of time after which virtual machine 3110 b should be recycled.TBAC module 110 may use timestamp 3120 and time threshold 3125 todetermine a time after which the virtual machine 3110 b should berecycled. As an example and not by way of limitation, TBAC module 110may add the time threshold 3125 to the timestamp 3120 to determine thattime.

In particular embodiments, recycling virtual machine 3110 b may includereplacing virtual machine 3110 b with a secured copy 3110 a of virtualmachine 3110 b. Secured copy 3110 a may have been generated and storedwhen virtual machine 3110 b was established. Secured copy 3110 a may bestored within memory 134. Although this disclosure describes securedcopy 3110 a being stored in TBAC module 110, this disclosurecontemplates secured copy 3110 a being stored in any suitable component.

TBAC module 110 may receive a token 115 that indicates a changeassociated with granting access to a resource 145. As an example and notby way of limitation, token 115 may indicate user 112 is requestingaccess to resource 145. Prior to granting access to resource 145, TBACmodule 110 may determine if device 114 has been provisioned a validvirtual machine 3110 b. If the virtual machine 3110 b is valid, accessto the resource 145 may be granted. As another example and not by way oflimitation, token 115 may be a hard token 115 g associated with device114 indicating the virtual machine 3110 b may be invalid. Although thisdisclosure describes token 115 indicating particular changes, thisdisclosure contemplates token 115 indicating any suitable change. Thischange could include any suitable communication, process, token, etc inthe system 100. In response to receiving token 115, TBAC module 110 maydetermine if the virtual machine 3110 b is invalid.

To make the determination whether the virtual machine 3110 b is valid,TBAC module 110 may use token 115 and VM token 115 i to access VMrecycling (RRR1) rules 3130. In particular embodiments, TBAC module 110may apply RRR1 rules 3130 to determine if virtual machine 3110 b isvalid based on timestamp 3120 and time threshold 3125. As an example andnot by way of limitation, RRR1 rules 3130 may specify that if thecurrent time exceeds the time threshold 3125 added to timestamp 3120,then TBAC module 110 may determine that virtual machine 3110 b isinvalid. Although this disclosure describes TBAC module 110 determiningthe validity of VM 3110 b in a particular manner, this disclosurecontemplates TBAC module 110 determining the validity of virtual machine3110 b in any suitable manner. For example, TBAC module 110 may examinethe status of a flag associated with virtual machine 3110 b. The flagmay be turned on when virtual machine 3110 b becomes invalid. If TBACmodule detects that the flag is on, TBAC module 110 may initiate therecycling process.

In response to a determination that the virtual machine 3110 b isinvalid, TBAC module 110 may initiate the virtual machine recyclingprocess by generating a recycle token 115 s. In particular embodiments,recycle token 115 s may include instructions to recycle virtual machine3110 b and information associated with the secured copy 3110 a ofvirtual machine 3110 b. TBAC module 110 may communicate recycle token115 s to facilitate the recycling of virtual machine 3110 b.

After recycle token 115 s has been communicated, virtual machine 3110 bmay begin recycling. In particular embodiments, virtual machine 3110 bmay be executing process 3140 when recycling is initiated. TBAC module110 may wait for virtual machine 3110 b to finish executing process 3140before recycling. In some embodiments, rather than wait for process 3140to finish, TBAC module 110 may facilitate the secure storage of a copyof the process 3140. After the virtual machine 3110 b finishesrecycling, TBAC module 110 may facilitate the recovery of the securedcopy of the process 3140, and the recycled virtual machine 3110 b maycomplete the process 3140.

To recycle virtual machine 3110 b, virtual machine 3110 b may bereplaced with the secured copy 3110 a of virtual machine 3110 b. TBACmodule 110 may send information about the location of the secured copy3110 a of virtual machine 3110 b using recycle token 115 s. Device 114may download the secured copy 3110 a of virtual machine 3110 b from thatlocation. After virtual machine 3110 b has been recycled, timestamp 3120and time threshold 3125 may be updated to reflect the recycling.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 31, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 31 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 31 includes all the elements of system 100in FIG. 1.

FIG. 32 is a flowchart illustrating a method 3200 of performing virtualmachine recycling. TBAC module 110 may perform method 3200. As providedby FIG. 32, TBAC module 110 may begin by storing a hard token 115 g,compliance token 115 h, VM token 115 i, subject token 115 k, resourcetoken 115 c, risk token 115 m, and session token 115 j, among others asappropriate in step 3210. In particular embodiments, VM token 115 i maybe associated with a virtual machine 3110 b. Virtual machine 3110 b maybe associated with a timestamp 3120 and a time threshold 3125. TBACmodule 110 may continue by storing a secured copy 3110 a of virtualmachine 3110 b in step 3220. At step 3230, TBAC module 110 may receive atoken 115 indicating a change associated with granting access to aresource 145. As an example and not by way of limitation, token 115 mayindicate that a user 112 is attempting to access resource 145.

In response, TBAC module 110 may access VM recycling (RRR1) rules 3130in step 3240. In step 3250, TBAC module 110 may determine, based on RRR1rules 3130, if the virtual machine 3110 b is still valid. If the virtualmachine 3110 b is still valid, TBAC module 110 may conclude. If thevirtual machine 3110 b is not valid, TBAC module 110 may generate arecycle token 115 s in step 3260. In particular embodiments, recycletoken 115 s may include the location of the secured copy 3110 a of thevirtual machine 3110 b. TBAC module 110 may also access the secured copy3110 a of the virtual machine 3110 b in step 3270. TBAC module 110 mayconclude by communicating the recycle token 115 s to facilitate thereplacing of the virtual machine 3110 b with the secured copy 3110 a ofthe virtual machine 3110 b in step 3280.

In particular embodiments, because system 100 may facilitate therecycling of virtual machine 3110 b, system 100 may provide a faster andmore seamless user experience to user 112. Furthermore, because TBACmodule 110 uses tokens 115 to monitor virtual machine 3110 b, system 100may determine more quickly when a virtual machine 3110 b needs to berecycled.

FIGS. 33 and 34 illustrate the system 100 performing token termination.In general, a user 112 may perform some action that will block access toa resource 145. For example, accessing a resource 145 that containsnumerous security holes may block access to another resource 145 that issensitive to risk. The process of determining whether access to aresource 145 should be blocked and enforcing that determination is knownas token termination, which is discussed further with respect to FIGS.33 and 34.

TBAC module 110 may track which resources 145 are non risk sensitiveresources 145 a and which are risk sensitive resources 145 b. If a user112 requests access to a risk sensitive resource 145 b while the user112 is exposing security risks, TBAC module 110 may perform tokentermination to block user 112 from accessing the risk sensitive resource145 b until the security risks are remedied.

FIG. 33 illustrates the system 100 of FIG. 1 performing tokentermination. As provided by FIG. 33, TBAC module 110 may store a hardtoken 115 g, subject token 115 k, first resource token 115 c 1, networktoken 115 f, risk token 115 m, and session token 115 j, among others asappropriate. First resource token 115 c 1 may be associated with a user112 accessing a non-risk sensitive resource 145 a. In particularembodiments, TBAC module 110 may receive a token 115 indicating a changeassociated with accessing a resource 145. As an example and not by wayof limitation, the token 115 may be a second resource token 115 c 2indicating that the user 112 is requesting access to a risk sensitiveresource 145 b. In particular embodiments, simultaneous access tonon-risk sensitive resource 145 a and risk sensitive resource 145 b maynot be allowed for security purposes. As an example and not by way oflimitation, non-risk sensitive resource 145 a may be a chat session andrisk sensitive resource 145 b may be a personal banking application. Thechat session may contain security holes that leave the personal bankingapplication vulnerable to potential hacks and malware. Therefore, it maynot be desirable to grant simultaneous access to the chat session andthe personal banking application.

When TBAC module 110 receives second resource token 115 c 2 indicatingthat a user 112 is requesting access to the risk sensitive resource 145b, TBAC module 110 may access token termination (TTT2) rules 3330 storedin memory 134 to determine if access to the non-risk sensitive resource145 a should be terminated prior to granting access to the risksensitive resource 145 b. In particular embodiments, a particular TTT2rule 3330 may specify that accessing a non-risk sensitive resource 145 arepresented by first resource token 115 c 1 may pose a security risk ifaccess to risk sensitive resource 145 b was granted simultaneously. Inthis case, TBAC module 110 may determine, based on TTT2 Rules 3330, thataccess to the non-risk sensitive resource 145 a should be terminatedbefore granting access to risk sensitive resource 145 b represented bysecond resource token 115 c 2.

TBAC module 110 may generate a decision token 115 n representing thedetermination to terminate access to the non-risk sensitive resource 145a. TBAC module 110 may communicate the decision token 115 n tofacilitate the termination of access to the non-risk sensitive resource.In particular embodiments, after access to the non-risk sensitiveresource 145 a has been terminated, TBAC module 110 may receive aresource token 115 c indicating that access to the non-risk sensitiveresource has been terminated. In response, TBAC module 110 may generatea second decision token 115 n 2 indicating that access to the risksensitive resource 145 b should be granted. In particular embodiments,TBAC module 110 may also terminate the first resource token 115 c 1 inresponse to receiving the resource token 115 c. TBAC module 110 maycommunicate the second decision token to facilitate the granting ofaccess to the risk sensitive resource 145 b. In particular embodiments,the second decision token 115 n 2 may be communicated to resourceprovider 140, which may grant access to the risk sensitive resource 145b after receiving the second decision token 115 n 2.

In particular embodiments, user 112 may be presented with the option toterminate access to the non-risk sensitive resource 145 a. If the user112 chooses not to terminate access to the non-risk sensitive resource145 a, the user 112 may be blocked from accessing the risk sensitiveresource 145 b.

In particular embodiments, user 112 may expose security risks throughother means than by accessing a non-risk sensitive resource 145 a. Forexample, user 112 may attach a peripheral device, such as a USB drive,to device 114. The peripheral device may present security risks. In thatcase, TBAC module 110 may receive a hard token 115 g indicating thatdevice 114 has a peripheral device attached. When user 112 requestsaccess to risk sensitive resource 145 b, TBAC module 110 may performtoken termination to block access to the risk sensitive resource 145 buntil user 112 removes the peripheral device. In particular embodiments,user 112 may attach the peripheral device while user 112 is accessingthe risk sensitive resource 145 b. In that case, TBAC module 110 maydetect the hard token 115 g and in response, perform token terminationto terminate access to the risk sensitive resource 145 b until user 112removes the peripheral device. After user 112 removes the peripheraldevice, TBAC module 110 may receive a second hard token 115 g indicatingthat the peripheral device has been removed. TBAC module 110 may thengenerate a decision token 115 n to facilitate access to the risksensitive resource 145 b.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 33, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 33 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 33 includes all the elements of system 100in FIG. 1. Although this disclosure describes particular user actionscreating a security hole, there could be any number of different waysthat a user's action, a resource parameter, a network condition, or anyother characteristic of system 100 could create a security hole thatneeds to be addressed before a user may be granted access to a risksensitive resource. This disclosure contemplates any of those potentialsecurity holes.

FIG. 34 is a flowchart illustrating a method 3400 of performing tokentermination. TBAC module 110 may perform the method 3400. As provided byFIG. 34, TBAC module 110 may begin by storing a hard token 115 b,subject token 115 k, first resource token 115 c 1, risk token 115 m,network token 115 f, and session token 115 j, among others asappropriate in step 3410. The first resource token 115 c 1 may beassociated with a user 112 accessing a non-risk sensitive resource 145a. TBAC module 110 may continue by receiving a second resource token 115c 2 indicating the user 112 is requesting access to a risk sensitiveresource 145 b in step 3420. In response, TBAC module 110 may accessTTT2 rules 3330 in step 3430. In step 3440, TBAC module 110 maydetermine, based on TTT2 rules 3330, if access to the non-risk sensitiveresource 145 a should be terminated before granting access to the risksensitive resource 145 b. If access to the non-risk sensitive resourceneed not be terminated, TBAC module 110 may continue to step 3450 togenerate a decision token 115 n representing a decision to grant accessto the risk sensitive resource 145 b. TBAC module 110 may thencommunicate the decision token 115 n to facilitate enforcement of thatdecision in step 3451.

If access to the non-risk sensitive resource should to be terminated,then TBAC module 110 may generate a decision token 115 n representingthe decision to terminate access to the non-risk sensitive resource 145a in step 3455. TBAC module 110 may then communicate the decision token115 n to facilitate the termination of access to the non-risk sensitiveresource 145 a in step 3456. After access to the non-risk sensitiveresource 145 a has been terminated, TBAC module 110 may receive aresource token 115 c indicating that access has been terminated in step3458. In response to receiving the resource token 115 c, TBAC module 110may generate a second decision token 115 n 2 indicating access to therisk sensitive resource 145 b should be granted in step 3462. TBACmodule 110 may then communicate the second decision token 115 n 2 tofacilitate access to the risk sensitive resource 145 b in step 3466.

In particular embodiments, because system 100 may perform tokentermination, system 100 may provide a more robust security system thatprovides for blocking access based on the risk sensitivity of theresources. Furthermore, because TBAC module 110 may terminate tokens115, system 100 may provide a faster and more efficient security system.

FIGS. 35 and 36 illustrate the system 100 performing tamper detection.In general, mechanical components of system 100 such as the device 114,network 120, or resource 145 may be the subject of attacks by viruses,malware, or hackers. When attacks happen, the tokens 115 associated withthose mechanical components may be affected. System 100 may detect whenthose components may be attacked by examining the tokens 115 associatedwith those components. The process of detecting when those componentshave been affected is known as tamper detection, which is discussedfurther with respect to FIGS. 35 and 36.

TBAC module 110 may store tokens 115 associated with the mechanicalcomponents of system 100 as well as secured copies of those tokens. Anattack on a component may affect the token 115 associated with thatcomponent. When a token 115 associated with a component changes, TBACmodule 110 may compare the token 115 with its corresponding secured copyto determine if the component has been attacked.

FIG. 35 illustrates the system 100 of FIG. 1 detecting tampering. Asprovided in FIG. 35, TBAC module 110 may store a hard token 115 g, anetwork toke 115 f, a subject token 115 k, a resource token 115 c, arisk token 115 m, and a session token 115 j. Hard token 115 g may beassociated with a device 114. Network token 115 f may be associated withnetwork 120 and resource token 115 c may be associated with a resource145. Device 114 may be consuming resource 145 over network 120.Furthermore, hard token 115 g, network token 115 f, and resource token115 c may have corresponding secured copies 115 gs, 115 fs, and 115 csstored in memory 134. The secured copies 115 gs, 115 fs, and 115 cs mayhave been generated when the corresponding tokens 115 g, 115 f, and 115c were first generated. Although this disclosure describes securedcopies 115 gs, 115 fs, and 115 cs stored in a particular component ofsystem 100, this disclosure contemplates secured copies 115 gs, 115 fs,and 115 cs stored in any suitable component of system 100.

In particular embodiments, TBAC module 110 may receive a suspect token115 t that indicates a risk that device 114, network 120, or resource145 may have been tampered. Tampering may include any security breachesby viruses, malware, or hackers. As an example and not by way oflimitation, suspect token 115 t may indicate that device 114 has beeninfected with a virus. As another example and not by way of limitation,suspect token 115 t may indicate that network 120 is beginning todistribute malware. As yet another example and not by way of limitation,suspect token 115 t may indicate that resource 145 is being targeted ina denial of service attack. Tampering of the device 114, network 120, orresource 145 may result in a change in any of the hard token 115 g,network token 115 f, or resource token 115 c.

TBAC module 110 may detect changes within hard token 115 g, networktoken 115 f, or resource token 115 c that resulted from tampering. Todetect these changes, TBAC module 110 may use suspect token 115 t toaccess token tampering (TTT3) rules 3530 stored in memory 134. Inparticular embodiments, TTT3 rules 3530 may specify which tokens 115 ofthe hard token 115 g, network token 115 f, and resource token 115 c mayhave been affect as a result of the risk indicated in suspect token 115t. TBAC module 110 may then compare the tokens 115 that may have beenchanged as a result of tampering with their corresponding securedcopies. As an example and not by way of limitation, suspect token 115 tmay indicate a risk that malware may be causing a denial of serviceattack. In that situation, TTT3 rules 3530 may specify that networktoken 115 f and resource token 115 c should be compared with theircorresponding secured copies 115 fs and 115 cs. If any differences thatresulted from tampering are detected during the comparisons, TBAC module110 may indicate that the token 115 containing that difference has beencompromised. As an example and not by way of limitation, if network 120is distributing malware but resource 145 is not experiencing a denial ofservice attack, then the comparisons may indicate that network token 115f is different from its corresponding secured copy 115 fs and that thatdifference may have resulted from tampering (e.g., malware infection).

In particular embodiments, in response to the determination that a token115 has been compromised as a result of tampering, TBAC module 110 mayreplace that token 115 with its corresponding secured copy. As anexample and not by way of limitation, if network token 115 f has beencompromised as a result of tampering, TBAC module 110 may replacenetwork token 115 f with its corresponding secured copy 115 fs. Incertain embodiments, TBAC module 110 may replace the tampered token 115by terminating the tampered token 115 and generating a new token 115that matches the corresponding secured copy of the tampered token 115.

In particular embodiments, TBAC module 110 may perform additional checksto determine if a token 115 has been tampered. As an example and not byway of limitation, TBAC module 110 may detect that a Kerberos token 115associated with device 114 may have been tampered. In addition tocomparing the Kerberos token 115 with its corresponding secured copy,TBAC module 110 may verify the integrity of a ticket associated with theKerberos token 115. If the ticket is valid, TBAC module 110 may treatthe valid ticket as an indication that the Kerberos token 115 has notbeen tampered. If the ticket is invalid, TBAC module 110 may treat theinvalid ticket as an indication that the Kerberos token 115 has beentampered.

In particular embodiments, TBAC module 110 may generate a revalidationtoken 115 u to indicate which tokens 115 have been compromised as aresult of tampering. As an example and not by way of limitation, ifnetwork token 115 f has been compromised because network 120 isdistributing malware, then revalidation token 115 u may indicate thatnetwork token 115 f has been compromised. In certain embodiments, TBACmodule 110 may communicate revalidation token 115 u to a token providercorresponding to the token 115 that was compromised as a result oftampering. As an example and not by way of limitation, TBAC module 110may communicate revalidation token 115 u to network token provider 122if network token 115 f was compromised as a result of tampering. Inparticular embodiments, revalidation token 115 u may be communicated tocomputed risk token provider 124 to compute or recomputed a risk token115 m. As an example and not by way of limitation, if a network token115 f is discovered to have been tampered, the risk associated withgranting access to a resource 145 over network 120 may increase.Computed risk token provider 124 may generate a risk token 115 mrepresenting that increase in risk. The risk token 115 m may then beused to facilitate the making of an access decision 900 following theprocess described with respect to FIGS. 8-10.

Although this disclosure describes TBAC module 110 performing certainactions with respect to FIG. 35, this disclosure contemplates theprocessor 132 and the memory 134 of the TBAC module 110 performing theseactions. The illustration of system 100 in FIG. 35 does not specificallyillustrate all of the elements from the illustration of system 100 inFIG. 1 so that particular aspects of system 100 may be emphasized.However, system 100 of FIG. 35 includes all the elements of system 100in FIG. 1.

FIG. 36 is a flowchart illustrating a method 3600 of detecting tamperingusing the system 100 of FIG. 1. TBAC module 110 may perform method 3600.As provided in FIG. 36, TBAC module 110 may begin by storing a hardtoken 115 g, subject token 115 k, resource token 115 c, risk token 115m, network token 115 f, and session token 115 j in step 3610. The hardtoken 115 g may be associated with a device 114. The network token 115 fmay be associated with network 120. The resource token 115 c may beassociated with a resource 145. TBAC module 110 may receive a suspecttoken 115 t indicating a risk that device 114, network 120, or resource145 has been tampered in step 3620. In response to receiving the suspecttoken 115 t, TBAC module 110 may access TTT3 rules 3530 in step 3630.TTT3 rules 3530 may specify which tokens 115 should be examined forpotential tampering.

TBAC module 110 may then compare the hard token 115 g, network token 115f, and/or resource token 115 c with secured copies of the hard token 115gs, network token 115 fs, and resource token 115 cs in step 3640. Instep 3650, TBAC module 110 may determine if any of the hard token 115 g,network token 115 f, and/or resource token 115 c differ from itscorresponding secured copy 115 gs, 115 fs, or 115 cs. If none of thetokens 115 differ from its corresponding secured copy, TBAC module 110may conclude. However, if any of the tokens differ from itscorresponding secured copy, TBAC module 110 may proceed to step 3660 togenerate a revalidation token 115 u representing the tokens 115 thatdiffer from their corresponding secured copies. TBAC module 110 may thenconclude by communicating the revalidation token 115 u to theappropriate token providers in step 3670. Communicating the revalidationtoken 115 u may facilitate the replacement of a tampered token 115 withits corresponding secured copy.

In particular embodiments, because system 100 may detect tampering,system 100 may provide a more responsive and robust security system.Furthermore, because TBAC module 110 uses tokens to monitor components,system 100 may respond faster to any attacks on those components.

FIGS. 37 and 38 are high level architectural diagrams of a system 3700that does not use tokens 115 and of a system 3800 that does use tokens115 respectively. System 3700 may include an Entitlement Engine thathandles directly attributes 425 associated with Interfaces A-E. Toaugment system 3700 to use tokens 115, system 3800 may include anadditional token layer that interacts with Interfaces A-E. The variousinterfaces and token layer will be discussed further with respect toFIGS. 37 and 38.

FIG. 37 is a high level architectural diagram of a system 3700 that doesnot use tokens 115 to control access to a resource 145. As provided inFIG. 37, the Entitlement Engine may make access decisions 900 bydirectly using attributes 425 associated with Interfaces A-E. InterfaceA may include attributes 425 associated with authentication (AuthN) suchas for example, device 114, service, and user 112 authentication.Interface A may further include attributes 425 associated with STS andFederation and XML Firewall Appliance. Interface B may includeattributes 425 associated with network 120 such as for example,firewalls, intrusion, and integrity. Interface C may include attributes425 associated with risk (similar to the attributes 425 represented byrisk token 115 m). Interface D may include attributes 425 associatedwith data (similar to attributes 425 associated with data token provider129). Interface E may include attributes 425 associated with accesscontrol management (akin to attributes 425 associated with privilegetokens 115 p) such as for example, attributes 425 associated withSecurity Event and Incident Management (SEIM), Governance Risk &Compliance (GRC), and auditing.

FIG. 38 is a high level architectural diagram of a system 3800 that usestoken 115 to control access to a resource 145. As provided by FIG. 38,system 3800 may add a layer that processes tokens 115 around theEntitlement Engine, which may now make access decisions 900 by usingtokens 115 associated with Interfaces A-E. For example, Interface A mayinclude tokens 115 associated with user 112 authentication, such as forexample, biometric tokens, RFID tokens, Rivest, Shamir, Adelman (RSA)tokens, SAML tokens, and XML tokens. These tokens may be similar tosubject tokens 115 k. Interface B may include tokens 115 associated withnetwork 120, such as for example, Posture/Priority tokens, Packet/Pathtokens, TPM tokens, TNC tokens, Transaction Security System (TSS)tokens, Integrity tokens, and Access Control List (ACL) tokens. Thesetokens 115 may be similar to network tokens 115 f. Interface C mayinclude tokens 115 associated with risk, such as for example, risktokens 115 m. Interface D may include tokens 115 associated with data ofuser 112, such as for example, data tokens 115 e. Interface D mayfurther include xRML tokens and Privilege/Permission tokens. Interface Emay include tokens 115 associated with access control management such asfor example, Event tokens, Audit tokens, and T-BAC module 110 tokens.

In particular embodiments, system 3800 may provide several advantagesover system 3700 by using tokens 115. First, system 3800 may be operableto align the function of tokens 115 with the appropriate OSI layerassociated with the tokens 115. Second, system 3800 may leverage theadvances made in token 115 technologies to improve security functions.Third, system 3800 may perform session control via session specificpolicies using tokens 115. Fourth, system 3800 may leverage the mappingof tokens 115 to attributes 425 for more efficient processing. Fifth,system 3800 may use tokens 115 to quickly and efficiently computeIdentity Assurance levels 940, trust levels 920, integrity levels 910,and risk levels 930 to make access decisions 900.

Although this disclosure describes system 100 using singular tokens 115a-u to perform the described functions, this disclosure contemplatessystem 100 using any suitable number and combination of tokens 115 a-uto perform the described functions.

Although the present invention has been described with severalembodiments, a myriad of changes, variations, alterations,transformations, and modifications may be suggested to one skilled inthe art, and it is intended that the present invention encompass suchchanges, variations, alterations, transformations, and modifications asfall within the scope of the appended claims.

What is claimed is:
 1. An apparatus comprising: a memory that stores aplurality of tokens indicating that a user is attempting to access aresource; and a processor that: determines a related resource thatshares a relationship with the resource, wherein: the resource is acomposite resource; the related resource is a sub-resource of thecomposite resource; and the related resource is accessed in conjunctionwith accessing the resource; receives a risk token computed based atleast in part upon the resource and the related resource; determines anumeric authorization level for the user based at least in part upon theplurality of tokens and the risk token, the numeric authorization levelindicating whether the user is authorized to access the resource,wherein the composite resource comprises at least one sub-resource thatthe user is not authorized to access based on the numeric authorizationlevel and at least one sub-resource that the user is authorized toaccess based on the numeric authorization level; compares the numericauthorization level to a numeric threshold; determines, based at leastin part on the comparison between the numeric authorization level andthe numeric threshold, that the user is authorized to access the relatedresource; communicates a decision token indicating that the user isauthorized to access the resource and the related resource; receives arecomputed risk token computed based at least in part upon: a form ofauthentication performed by the user; and the presence of networkjitter; re-determines determine the numeric authorization level based atleast in part upon the recomputed risk token; determines, based at leastin part upon the recomputed risk token, that the user is authorized toaccess the at least one sub-resource; and communicates a second decisiontoken indicating that the user is authorized to access the resource, therelated resource, and the at least one sub-resource.
 2. The apparatus ofclaim 1, the memory further stores a plurality of token-based rules,wherein a token-based rule facilitates the determination of the relatedresource.
 3. The apparatus of claim 1, wherein the determination of therelated resource is based on a token-based rule.
 4. A method fordetermining resource contexts comprising: storing a plurality of tokensindicating that a user is attempting to access a resource; determining,by the processor, a related resource that shares a relationship with theresource, wherein: the resource is a composite resource; the relatedresource is a sub-resource of the composite resource; and the relatedresource is accessed in conjunction with accessing the resource;receiving a risk token computed based at least in part upon the resourceand the related resource; determining, by a processor, a numericauthorization level for the user based at least in part upon theplurality of tokens and the risk token, the numeric authorization levelindicating whether the user is authorized to access the resource,wherein the composite resource comprises at least one sub-resource thatthe user is not authorized to access based on the numeric authorizationlevel and at least one sub-resource that the user is authorized toaccess based on the numeric authorization level; comparing, by theprocessor, the numeric authorization level to a numeric threshold;determining, by the processor, based at least in part on the comparisonbetween the numeric authorization level and the numeric threshold, thatthe user is authorized to access the related resource; communicating adecision token indicating that the user is authorized to access theresource and the related resource; receiving a recomputed risk tokencomputed based at least in part upon: a form of authentication performedby the user; and the presence of network jitter; re-determining, by theprocessor, the numeric authorization level based at least in part uponthe recomputed risk token; determining, by the processor, based at leastin part upon the recomputed risk token, that the user is authorized toaccess the at least one sub-resource; and communicating a seconddecision token indicating that the user is authorized to access theresource, the related resource, and the at least one sub-resource. 5.The method of claim 4, further comprising storing a plurality oftoken-based rules, wherein a token-based rule facilitates thedetermination of the related resource.
 6. The method of claim 4, whereinthe determination of the related resource is based on a token-basedrule.
 7. One or more computer-readable non-transitory storage mediaembodying software that when executed: stores a plurality of tokensindicating that a user is attempting to access a resource; anddetermines a related resource that shares a relationship with theresource, wherein: the resource is a composite resource; the relatedresource is a sub-resource of the composite resource; and the relatedresource is accessed in conjunction with accessing the resource;receives a risk token computed based at least in part upon the resourceand the related resource; determines a numeric authorization level forthe user based at least in part upon the plurality of tokens and therisk token, the numeric authorization level indicating whether the useris authorized to access the resource, wherein the composite resourcecomprises at least one sub-resource that the user is not authorized toaccess and at least one sub-resource that the user is authorized toaccess; compares the numeric authorization level to a numeric threshold;determines, based at least in part on the comparison between the numericauthorization level and the numeric threshold, that the user isauthorized to access the related resource; communicates a decision tokenindicating that the user is authorized to access the resource and therelated resource; receives a recomputed risk token computed based atleast in part upon: a form of authentication performed by the user; andthe presence of network jitter; re-determines determine the numericauthorization level based at least in part upon the recomputed risktoken; determines, based at least in part upon the recomputed risktoken, that the user is authorized to access the at least onesub-resource; and communicates a second decision token indicating thatthe user is authorized to access the resource, the related resource, andthe at least one sub-resource.
 8. The media of claim 7 embodyingsoftware that when executed further stores a plurality of token-basedrules, wherein a token-based rule facilitates the determination of therelated resource.
 9. The media of claim 7, wherein the determination ofthe related resource is based on a token-based rule.